End-to-end paths for web services - RESTful services
Use Java API for RESTful Web Services (JAX-RS) to develop services that follow Representational State Transfer (REST) principles. RESTful services are based on manipulating resources. Resources can contain static or dynamically updated data. By identifying the resources in the application, we can make the service more useful and easier to develop.
Subtopics
- Implement JAX-RS web applications
- Use XML content in JAX-RS application requests and responses
- Use JSON content in JAX-RS application requests and responses
- Use Atom content in JAX-RS application requests and responses
- Use custom entity formats
- Use content negotiation to serve multiple content types in JAX-RS applications
- Use JAX-RS context objects to obtain more information about requests
- Implement RESTful views of EJB applications using JAX-RS
- Use Java contexts and dependency injection with JAX-RS
- Use handlers to enhance request and response processing
- Use multipart content in JAX-RS application requests and responses
- Use multipart/form-data content in JAX-RS application requests and responses
- Implement secure JAX-RS applications
- Use WADL to generate service documentation
- Use the Apache Wink REST client inside server applications to issue requests
- Use the Apache Wink REST client as a stand-alone thin client
- Use JAX-RS 2.0 client as a stand-alone thin client
End-to-end paths for web services End-to-end paths for web services - Addressing (WS-Addressing) End-to-end paths for web services - Reliable messaging (WS-ReliableMessaging) End-to-end paths for web services - Policy (WS-Policy) End-to-end paths for web services - UDDI registry End-to-end paths for web services - Resource framework (WSRF) End-to-end paths for web services - Security (WS-Security) End-to-end paths for web services - Transaction support (WS-Transaction) End-to-end paths for web services - Transports