Jersey 2.0-m13 User Guide

List of Examples

3.1. Simple hello world root resource class

3.2. Specifying URI path parameter

3.3. PUT method

3.4. Specifying output MIME type

3.5. Using multiple output MIME types

3.6. Server-side content negotiation

3.7. Specifying input MIME type

3.8. Query parameters

3.9. Custom Java type for consuming request parameters

3.10. Processing POSTed HTML form

3.11. Obtaining general map of URI path and/or query parameters

3.12. Obtaining general map of header parameters

3.13. Obtaining general map of form parameters

3.14. Example of the bean which will be used as @BeanParam

3.15. Injection of MyBeanParam as a method parameter:

3.16. Injection of more beans into one resource methods:

3.17. Sub-resource methods

3.18. Sub-resource locators

3.19. Injection

4.1. Using File with a specific MIME type to produce a response

4.2. Returning 201 status code and adding Location header in response to POST request

4.3. Adding an entity body to a custom response

4.4. Throwing Jersey specific exceptions to control response

4.5. Jersey specific exception implementation

4.6. Mapping generic exceptions to responses

4.7. Conditional GET support

5.1. URI building

5.2. Building URIs using query parameters

6.1. Deployment agnostic application model

6.2. Reusing Jersey implementation in your custom application model

6.3. Deployment of a JAX-RS application using @ApplicationPath with Servlet 3.0

6.4. Configuration of maven-war-plugin in pom.xml with Servlet 3.0

6.5. Deployment of a JAX-RS application using web.xml with Servlet 3.0

6.6. Deployment of your application using Jersey specific servlet

6.7. Using Jersey specific servlet without an application model instance

7.1. POST request with form parameters

14.1. Accessing SecurityContext

18.1. Jersey 1 reloader implementation

18.2. Jersey 1 reloader registration

18.3. Jersey 2 reloader implementation

18.4. Jersey 2 reloader registration