End-to-end paths for web services - RESTful services

Java API for RESTful Web Services (JAX-RS) services follow Representational State Transfer (REST) principles based on manipulating application resources containing static or dynamically updated data.

See:

• Implement JAX-RS web applications
• Use XML content requests and responses
• Use JSON content requests and responses
• Use Atom content requests and responses
• Use custom entity formats
• Use content negotiation to serve multiple content types
• Use JAX-RS context objects to obtain more information about requests
• Implement RESTful views of EJB applications
• Use Java contexts and dependency injection
• Use handlers to enhance request and response processing
• Use multipart content requests and responses
• Use multipart/form-data content 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

Related :
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