This is more of a general question about the difference between `text/xml` and `application/xml`.
I am fairly new to writing webservices (REST - Jersey). I have been producing `application/xml` since it is what shows up in most tutorials / code examples that I have been using to learn, but I recently found out about `text/xml` and was wondering what is different about it and when would you use it over `application/xml`?

What&#39;s the difference between text/xml vs application/xml for webservice response

I&#39;m learning JAX-RS (aka, JSR-311) using Jersey. I&#39;ve successfuly created a Root Resource and am playing around with parameters:

    @Path(&quot;/hello&quot;)
    public class HelloWorldResource {

        @GET
        @Produces(&quot;text/html&quot;)
        public String get(
    		@QueryParam(&quot;name&quot;) String name,
    		@QueryParam(&quot;birthDate&quot;) Date birthDate) {

             // Return a greeting with the name and age
        }
    }

This works great, and handles any format in the current locale which is understood by the Date(String) constructor (like YYYY/mm/dd and mm/dd/YYYY). But if I supply a value which is invalid or not understood, I get a 404 response.

For example:

&lt;!-- language: none --&gt;

    GET /hello?name=Mark&amp;birthDate=X

    404 Not Found

How can I customize this behavior? Maybe a different response code (probably &quot;400 Bad Request&quot;)? What about logging an error? Maybe add a description of the problem (&quot;bad date format&quot;) in a custom header to aid troubleshooting? Or return a whole Error response with details, along with a 5xx status code?


JAX-RS / Jersey how to customize error handling?

I confused with the difference between **JAX-RS** (well, maybe should use Jersey to do comparison since JAX-RS is just spec) and **Spring for Restful services**. I tried to search for more information online and it become more confusing. My company is using Spring MVC to develop Restful APIs

The confusing part is, JAX-RS stands for **Java API for RESTful Web Services**, in Spring i am also using java to develop RESTful Web Services, so i don&#39;t actually get the differences. Does Spring follow the JAX-RS specifications?

From what i know until now:

 1. JAX-RS is a blueprint/specification, it has Jersey, RESTeasy, etc as implementations.
 

Difference between JAX-RS and Spring Rest

Could anyone explain to me what a JAX-RS Provider is and what ‘@Provider’ annotation does? I have been reading documentation but I cant get it.  
If there are resource classes that service the incoming requests, what do Providers do? How are they different from singleton resource classes when I create a persistent resource class (the one that is not per-request)? Or are those classes also providers?


What does Provider in JAX-RS mean?

My POST method looks like this:

    @POST
    @Consumes({&quot;application/json&quot;})
    @Path(&quot;create/&quot;)
    public void create(String param1, String param2){
        System.out.println(&quot;param1 = &quot; + param1);
        System.out.println(&quot;param2 = &quot; + param2);
    }

When I create a Jersey Client in Netbeans the method who calls the post method looks like this:

    public void create(Object requestEntity){
        webResource.path(&quot;create&quot;).type(MediaType.APPLICATION_JSON).post(requestEntity);
    }

When running this test:

    @Test
    public void hello(){
        String json = &quot;{param1=\&quot;hello\&quot;,param2=\&quot;hello2\&quot;}&quot;;
        this.client.create(json);
    }

It gives the following output in the server:

    INFO: param1 = {param1=&quot;hello&quot;,param2=&quot;hello2&quot;}
    INFO: param2 = 

What do I need to change so that the parameters are giving the correct value?


How to access parameters in a RESTful POST method

We are planning a project primarily serving content to mobile apps, but need to have a website.

My question is whether is makes sense to use Jersey or Restlet to develop REST APIs for our mobile apps, and then use Play! to serve the website. 

Or does it make more sense to just use Play! to do it all? If so, how to do REST with Play! framework? 

RESTful on Play! framework

I&#39;m using Jersey to implement a RESTful API that is primarily retrieve and serve JSON encoded data. But I have some situations where I need to accomplish the following:

* Export downloadable documents, such as PDF, XLS, ZIP, or other binary files.
* Retrieve multipart data, such some JSON plus an uploaded XLS file

I have a single-page JQuery-based web client that creates AJAX calls to this web service. At the moment, it doesn&#39;t do form submits, and uses GET and POST (with a JSON object). Should I utilize a form post to send data and an attached binary file, or can I create a multipart request with JSON plus binary file?

My application&#39;s service layer currently creates a ByteArrayOutputStream when it generates a PDF file. What is the best way to output this stream to the client via Jersey? I&#39;ve created a MessageBodyWriter, but I don&#39;t know how to use it from a Jersey resource. Is that the right approach?

I&#39;ve been looking through the samples included with Jersey, but haven&#39;t found anything yet that illustrates how to do either of these things. If it matters, I&#39;m using Jersey with Jackson to do Object-&gt;JSON without the XML step and am not really utilizing JAX-RS. 

Input and Output binary streams using JERSEY?

I&#39;ve just started to develop REST services, but I&#39;ve come across a difficult situation: sending files from my REST service to my client. So far I&#39;ve gotten the hang of how to send simple data types (strings, integers, etc) but sending a file is a different matter since there are so many file formats that I don&#39;t know where I should even begin. My REST service is made on Java and I&#39;m using Jersey, I&#39;m sending all the data using the JSON format.

I&#39;ve read about base64 encoding, some people say it&#39;s a good technique, others say it isn&#39;t because of file size issues. What is the correct way? This is how a simple resource class in my project is looking:

    import java.sql.SQLException;
    import java.util.List;
    
    import javax.ws.rs.GET;
    import javax.ws.rs.Path;
    import javax.ws.rs.Produces;
    import javax.ws.rs.core.Context;
    import javax.ws.rs.core.MediaType;
    import javax.ws.rs.core.Request;
    import javax.ws.rs.core.UriInfo;
    
    import com.mx.ipn.escom.testerRest.dao.TemaDao;
    import com.mx.ipn.escom.testerRest.modelo.Tema;
    
    @Path(&quot;/temas&quot;)
    public class TemaResource {
    		
    	@GET
    	@Produces({MediaType.APPLICATION_JSON})
    	public List&lt;Tema&gt; getTemas() throws SQLException{
    
    		TemaDao temaDao = new TemaDao();		
    		List&lt;Tema&gt; temas=temaDao.getTemas();
    		temaDao.terminarSesion();
    		
    		return temas;
    	}
    }

I&#39;m guessing the code for sending a file would be something like:

    import java.sql.SQLException;
    
    import javax.ws.rs.GET;
    import javax.ws.rs.Path;
    import javax.ws.rs.Produces;
    
    @Path(&quot;/resourceFiles&quot;)
    public class FileResource {
    		
    	@GET
    	@Produces({application/x-octet-stream})
    	public File getFiles() throws SQLException{ //I&#39;m not really sure what kind of data type I should return
    
    		// Code for encoding the file or just send it in a data stream, I really don&#39;t know what should be done here
    		
    		return file;
    	}
    }

What kind of annotations should I use? I&#39;ve seen some people recommend for a `@GET` using `@Produces({application/x-octet-stream})`, is that the correct way? The files I&#39;m sending are specific ones so the client doesn&#39;t need to browse through the files. Can anyone guide me into how am I supposed to send the file? Should I encode it using base64 to send it as a JSON object? or the encoding isn&#39;t necessary to send it as a JSON object? Thanks for any help you may give.

what&#39;s the correct way to send a file from REST web service to client?

Starting from scratch without any previous Jersey 1.x knowledge, I&#39;m having a hard time understanding how to setup dependency injection in my Jersey 2.0 project.  

I also understand that HK2 is available in Jersey 2.0, but I cannot seem to find docs that help with Jersey 2.0 integration.

&lt;!-- language: lang-java --&gt;

    @ManagedBean
    @Path(&quot;myresource&quot;)
    public class MyResource {
    
        @Inject
        MyService myService;
    
        /**
         * Method handling HTTP GET requests. The returned object will be sent
         * to the client as &quot;text/plain&quot; media type.
         *
         * @return String that will be returned as a text/plain response.
         */
        @GET
        @Produces(MediaType.APPLICATION_JSON)
        @Path(&quot;/getit&quot;)
        public String getIt() {
            return &quot;Got it {&quot; + myService + &quot;}&quot;;
        }
    }

    @Resource
    @ManagedBean
    public class MyService {
        void serviceCall() {
            System.out.print(&quot;Service calls&quot;);
        }
    }

pom.xml

&lt;!-- language: lang-xml --&gt;

    &lt;properties&gt;
        &lt;jersey.version&gt;2.0-rc1&lt;/jersey.version&gt;
        &lt;project.build.sourceEncoding&gt;UTF-8&lt;/project.build.sourceEncoding&gt;
    &lt;/properties&gt;

    &lt;dependencyManagement&gt;
        &lt;dependencies&gt;
            &lt;dependency&gt;
                &lt;groupId&gt;org.glassfish.jersey&lt;/groupId&gt;
                &lt;artifactId&gt;jersey-bom&lt;/artifactId&gt;
                &lt;version&gt;${jersey.version}&lt;/version&gt;
                &lt;type&gt;pom&lt;/type&gt;
                &lt;scope&gt;import&lt;/scope&gt;
            &lt;/dependency&gt;
        &lt;/dependencies&gt;
    &lt;/dependencyManagement&gt;
    
    &lt;dependencies&gt;
        &lt;dependency&gt;
            &lt;groupId&gt;org.glassfish.jersey.core&lt;/groupId&gt;
            &lt;artifactId&gt;jersey-common&lt;/artifactId&gt;
        &lt;/dependency&gt;
        &lt;dependency&gt;
            &lt;groupId&gt;org.glassfish.jersey.core&lt;/groupId&gt;
            &lt;artifactId&gt;jersey-server&lt;/artifactId&gt;
        &lt;/dependency&gt;
        &lt;dependency&gt;
            &lt;groupId&gt;org.glassfish.jersey&lt;/groupId&gt;
            &lt;artifactId&gt;jax-rs-ri&lt;/artifactId&gt;
        &lt;/dependency&gt;
    &lt;/dependencies&gt;

I can get the container to start and serve up my resource, but as soon as I add @Inject to MyService, the framework throws an exception:

    SEVERE: Servlet.service() for servlet [com.noip.MyApplication] in context with path [/jaxrs] threw exception [A MultiException has 3 exceptions.  They are:
    1. org.glassfish.hk2.api.UnsatisfiedDependencyException: There was no object available for injection at Injectee(requiredType=MyService,parent=MyResource,qualifiers={}),position=-1,optional=false,self=false,unqualified=null,1039471128)
    2. java.lang.IllegalArgumentException: While attempting to resolve the dependencies of com.noip.MyResource errors were found
    3. java.lang.IllegalStateException: Unable to perform operation: resolve on com.noip.MyResource
    ] with root cause
    org.glassfish.hk2.api.UnsatisfiedDependencyException: There was no object available for injection at Injectee(requiredType=MyService,parent=MyResource,qualifiers={}),position=-1,optional=false,self=false,unqualified=null,1039471128)
    	at org.jvnet.hk2.internal.ThreeThirtyResolver.resolve(ThreeThirtyResolver.java:74)

&lt;br&gt;
My starter project is available at GitHub: https://github.com/donaldjarmstrong/jaxrs

Dependency injection with Jersey 2.0

I am newbie in RESTful jersey. I would like to ask what is the different between `@PathParam` and `@QueryParam` in jersey?

What is the difference between @PathParam and @QueryParam

I&#39;d like Jackson to deserialize a class with the following constructor:

    public Clinic(String name, Address address)

Deserializing the first argument is easy. The problem is that Address is defined as:

    public class Address {
      private Address(Map&lt;LocationType, String&gt; components)
      ...
    
      public static class Builder {
        public Builder setCity(String value);
        public Builder setCountry(String value);
        public Address create();
      }
    }

and is constructed like this: `new Address.Builder().setCity(&quot;foo&quot;).setCountry(&quot;bar&quot;).create();`

Is there a way to get key-value pairs from Jackson in order to construct the Address myself? Alternatively, is there a way to get Jackson to use the Builder class itself?

Jackson + Builder Pattern?

I really cant understand what really is jersey..

What I know is that Jax-RS is an API for building REST web services, and jersey?
I got some information and all say the same: &quot;jersey is an implementation of Jax-RS&quot;. But what it means?

If jax-rs is an API, why we need jersey for create a rest web service? Is jersey a couple of more libs to aim with jax-rs? if yes, jax-rs is an incomplete API?

What difference between Jersey vs jax-rs

How can I view the actual request that Jersey generates and sends to the server?  I am having issues with a particular request and the fellow running the webserver asked to see the full request (with headers and the such).

Jersey: Print the actual request

I am building a generic web service and need to grab all the query parameters into one string for later parsing. How can I do this?

How can I grab all query parameters in Jersey JaxRS?

I&#39;m creating a Jersey client for a GET service that has a List as query parameter. According to the [documentation](http://jersey.java.net/nonav/documentation/latest/user-guide.html#d4e247), it&#39;s possible to have a List as a query parameter (this information is also at [@QueryParam](http://jsr311.java.net/nonav/releases/1.1/javax/ws/rs/QueryParam.html) javadoc), check it out: 

&gt; In general the Java type of the method parameter may:
&gt;
&gt; 1. Be a primitive type;
&gt; 2. Have a constructor that accepts a single String argument;
&gt; 3. Have a static method named valueOf or fromString that accepts a single String argument (see, for example, Integer.valueOf(String) and java.util.UUID.fromString(String)); or
&gt; 4. Be List&lt;T&gt;, Set&lt;T&gt; or SortedSet&lt;T&gt;, where T satisfies 2 or 3 above. The resulting collection is read-only.
&gt;
&gt; Sometimes parameters may contain more than one value for the same name. If this is the case then types in 4) may be used to obtain all values.

However, I can&#39;t figure out how to add a List query parameter using Jersey client. 

I understand alternative solutions are: 

 1. Use POST instead of GET; 
 2. Transform the List into a JSON string and pass it to the service. 

The first one is not good, because the proper HTTP verb for the service is GET. It is a data retrieval operation. 

The second will be my option if you can&#39;t help me out. :)

I&#39;m also developing the service, so I may change it as needed. 

Thanks!

**Update**

Client code (using json)

    Client client = Client.create();
    
    WebResource webResource = client.resource(uri.toString());
    
    SearchWrapper sw = new SearchWrapper(termo, pagina, ordenacao, hits, SEARCH_VIEW, navegadores);
    
    MultivaluedMap&lt;String, String&gt; params = new MultivaluedMapImpl();
    params.add(&quot;user&quot;, user.toUpperCase()); 
    params.add(&quot;searchWrapperAsJSON&quot;, (new Gson()).toJson(sw));

    ClientResponse clientResponse = webResource .path(&quot;/listar&quot;)
                                                .queryParams(params)
                                                .header(HttpHeaders.AUTHORIZATION, AuthenticationHelper.getBasicAuthHeader())
                                                .get(ClientResponse.class);

    SearchResultWrapper busca = clientResponse.getEntity(new GenericType&lt;SearchResultWrapper&gt;() {});


Jersey client: How to add a list as query parameter

Sorry, this questions sounds silly, but after developing some of my RESTful services using Jersey, I asked myself the question -- If REST is just an architecture, and not a protocol like SOAP, why do we need a specification like JAX-RS?

I actually googled for questions like &quot;What is the difference between servlets and RESTful services over HTTP&quot; and to sum up the community answers, I got:

1. RESTful service development (on Jersey) is an architecture, which inherently uses servlets.
2. JAX-RS compliant tools like Jersey provide easy marshalling-unmarshalling of XML/JSON data, helping the developers.
3. REST helps us use GET/POST/PUT/DELETE in a fashion that is far efficient than normal servlets.

According to these answers, I guess if I write a servlet which uses JAXB (for dealing with automatic serialization), and I efficiently use GET/POST/PUT/DELETE in my servlet code, I don&#39;t use a tool like Jersey, and hence JAX-RS.

I know I am terribly wrong passing this statement, please correct me.

PS: This doubt actually came in when I had to develop some RESTful services in PHP. After going on through some of the RESTful PHP codes, I realized they are just the same old PHP scripts, with some helper methods for handling XML/JSON.



Why use JAX-RS / Jersey?

I am trying to build a simple hello world application for two days using Jersey + Google app engine. For simple AppEngine project I followed these tutorials and both works just fine
https://developers.google.com/appengine/docs/java/gettingstarted/creating
https://developers.google.com/appengine/docs/java/webtoolsplatform

But now I am trying to add Jersey and following this tutorial http://www.vogella.com/articles/REST/article.html.

But server keeps giving me 

&gt; java.lang.ClassNotFoundException: com.sun.jersey.spi.container.servlet.ServletContainer


when I add these lines in *web.xml*:

    &lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
    &lt;web-app xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
	xmlns=&quot;http://java.sun.com/xml/ns/javaee&quot; xmlns:web=&quot;http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd&quot;
	xsi:schemaLocation=&quot;http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd&quot;
	id=&quot;WebApp_ID&quot; version=&quot;2.5&quot;&gt;
	&lt;display-name&gt;TestServer&lt;/display-name&gt;
    &lt;servlet&gt;
		&lt;servlet-name&gt;Jersey REST Service&lt;/servlet-name&gt;
		&lt;servlet-class&gt;com.sun.jersey.spi.container.servlet.ServletContainer&lt;/servlet-class&gt;
		&lt;init-param&gt;
			&lt;param-name&gt;com.sun.jersey.config.property.packages&lt;/param-name&gt;
			&lt;param-value&gt;com.test.myproject&lt;/param-value&gt;
		&lt;/init-param&gt;
		&lt;load-on-startup&gt;1&lt;/load-on-startup&gt;
	&lt;/servlet&gt;
	&lt;servlet-mapping&gt;
		&lt;servlet-name&gt;Jersey REST Service&lt;/servlet-name&gt;
		&lt;url-pattern&gt;/rest/*&lt;/url-pattern&gt;
	&lt;/servlet-mapping&gt;
    &lt;/web-app&gt;

I have downloaded Jersey `JAX-RS 2.1 RI bundle` from [here][1] and have added all jar files in `WEB-INF/lib` folder as described in tutorial. And even after two days nothing is working. I have searched several times on Google and apparently people who are using Maven have solved it somehow but I am not using Maven neither did the guy who wrote that tutorial. 

Just to check if even `com.sun.jersey.spi.container.servlet.ServletContainer` exists in imported  `Jersey jars` I tried to just write this fully qualified name in Java and let the intellisense finish names but I couldn&#39;t get any intellisense after `com.sun.je` so my last guess is that there have been some **package rearrangement** in latest Jersey build and `jersey` is no longer inside `com.sun`. I am exhausted and I would appreciate any kind of help. 


  [1]: https://jersey.java.net/download.html

java.lang.ClassNotFoundException: com.sun.jersey.spi.container.servlet.ServletContainer

I have seen a lot of Jersey tutorials that starts with something like

    @ApplicationPath(&quot;services&quot;)
    public class JerseyApplication extends ResourceConfig {
    	public JerseyApplication() {
    		packages(&quot;com.abc.jersey.services&quot;);
    	}
    }

without explaining what exactly the `ResourceConfig` class is. So where can I find its documentation, usage, etc.? Googling for &quot;jersey resourceconfig&quot; does not yield any official doc.

Some of my questions about this class and its usage are:

 - What things can I do inside the subclass of `ResourceConfig`? 
 - Do I need to register the subclass of `ResourceConfig` somewhere so that it can be found or is it automatically detected by Jersey? 
 - If the subclass is automatically detected what happens if I have multiple subclasses of `ResourceConfig`?
 - Is the purpose of `ResourceConfig` the same as the `web.xml` file? If so what happens if I have both in my project? Does one of them take precedence over the other?

What exactly is the ResourceConfig class in Jersey 2?

What is the difference between `com.sun.jersey` and `org.glassfish.jersey`?

Currently I have my REST service working on `com.sun.jersey` and I want to write tests, but I can&#39;t find a good tutorial for this (nothing seems to work). However, I can find good documentation about the `org.glassfish.jersey` tests.

Difference com.sun.jersey and org.glassfish.jersey

I would like to create a RESTful app on Google App Engine. I would like to provide XML and JSON services. I have briefly experimented with Restlet, Resteasy, and Jersey. I haven&#39;t had much success with any of them, other than some simple examples in Restlet.

Could you share your experiences creating a Restful web application on Google App Engine using Java or provide any insight on the aforementioned toolkits on GAE?

Thanks!

Edit (2009-07-25):

I have decided to use Restlet for the time being. It seems to work flawlessly so far. Please post any other insights/opinions you may have. What problems have you encountered? Have you successfully used Jersey/Restlet/Resteasy on GAE/J? If so, we want to hear about it!

RESTful application on Google App Engine Java?

What&#39;s going wrong here?

    The ResourceConfig instance does not contain any root resource classes.
    Dec 10, 2010 10:21:24 AM com.sun.jersey.spi.spring.container.servlet.SpringServlet initiate
    SEVERE: Exception occurred when intialization
    com.sun.jersey.api.container.ContainerException: The ResourceConfig instance does not contain any root resource classes.
            at com.sun.jersey.server.impl.application.RootResourceUriRules.&lt;init&gt;(RootResourceUriRules.java:103)
            at com.sun.jersey.server.impl.application.WebApplicationImpl._initiate(WebApplicationImpl.java:1182)
            at com.sun.jersey.server.impl.application.WebApplicationImpl.access$600(WebApplicationImpl.java:161)
            at com.sun.jersey.server.impl.application.WebApplicationImpl$12.f(WebApplicationImpl.java:698)
            at com.sun.jersey.server.impl.application.WebApplicationImpl$12.f(WebApplicationImpl.java:695)
            at com.sun.jersey.spi.inject.Errors.processWithErrors(Errors.java:197)
            at com.sun.jersey.server.impl.application.WebApplicationImpl.initiate(WebApplicationImpl.java:695)
            at com.sun.jersey.spi.spring.container.servlet.SpringServlet.initiate(SpringServlet.java:117)

Filter:

    &lt;filter&gt;
        &lt;filter-name&gt;JerseyFilter&lt;/filter-name&gt;
        &lt;filter-class&gt;com.sun.jersey.spi.spring.container.servlet.SpringServlet&lt;/filter-class&gt;

        &lt;init-param&gt;
            &lt;param-name&gt;com.sun.jersey.config.feature.Redirect&lt;/param-name&gt;
            &lt;param-value&gt;true&lt;/param-value&gt;
        &lt;/init-param&gt;

        &lt;init-param&gt;
            &lt;param-name&gt;com.sun.jersey.config.property.JSPTemplatesBasePath&lt;/param-name&gt;
            &lt;param-value&gt;/views/&lt;/param-value&gt;
        &lt;/init-param&gt;

        &lt;init-param&gt;
            &lt;param-name&gt;com.sun.jersey.config.property.WebPageContentRegex&lt;/param-name&gt;
            &lt;param-value&gt;/(images|css|jsp)/.*&lt;/param-value&gt;
        &lt;/init-param&gt;
    &lt;/filter&gt;

    &lt;filter-mapping&gt;
        &lt;filter-name&gt;JerseyFilter&lt;/filter-name&gt;
        &lt;url-pattern&gt;/myresource/*&lt;/url-pattern&gt;
    &lt;/filter-mapping&gt;

Code:

    @Path (&quot;/admin&quot;)
    public class AdminUiResource {

      @GET
      @Produces (&quot;text/html&quot;)
      @Path (&quot;/singup&quot;)
      public Viewable getSignUp () {
        return new Viewable(&quot;/public/signup&quot;, &quot;Test&quot;);
      }
    }


The ResourceConfig instance does not contain any root resource classes

Can someone post an example of how in Jersey to set `StreamingOutput` as an entity in a `Response` object?

I haven&#39;t been able to find an example of this.

Example of using StreamingOutput as Response entity in Jersey

I&#39;m developing a java script client application, in server-side I need to handle CORS, all the services I had written in JAX-RS with JERSEY.
My code:
       
    @CrossOriginResourceSharing(allowAllOrigins = true)
    @GET
    @Path(&quot;/readOthersCalendar&quot;)
    @Produces(&quot;application/json&quot;)
    public Response readOthersCalendar(String dataJson) throws Exception {  
         //my code. Edited by gimbal2 to fix formatting
         return Response.status(status).entity(jsonResponse).header(&quot;Access-Control-Allow-Origin&quot;, &quot;*&quot;).build();
    }

As of now, i&#39;m getting error No &#39;Access-Control-Allow-Origin&#39; header is present on the requested resource. Origin &#39;http://localhost:8080&#39; is therefore not allowed access.”

Please assist me with this.

Thanks &amp; Regards
Buddha Puneeth

How to handle CORS using JAX-RS with Jersey

What do you think is the advantages/disadvantages between this two libraries? Which of these two are best suited for production environment? By the way I will be using JSON instead of XML.

I also would like to know what library is most supported by the community e.g. tutorials, documentation.

Java REST implementation: Jersey vs CXF

I just heard about [Apache Wink][1], and I was wondering what differences it had compared to [Jersey][2] or [JBoss RESTEasy][3].  What can be done in one that the other two can&#39;t?

We&#39;ve been using Jersey for some of our internal projects mostly for it&#39;s simplicity, but I can&#39;t really figure out what makes these other two any better that I would consider switching.  Does anyone have any use-cases for which niche each of these fills?

 [1]: http://incubator.apache.org/wink/
 [2]: http://jersey.java.net/
 [3]: http://jboss.org/resteasy

How to choose between Jersey, Apache Wink and JBoss RESTEasy?

I am using the Jersey implementation of JAX-RS. I would like to POST a JSON object to this service but I am getting an error code 415 Unsupported Media Type. What am I missing?

Here&#39;s my code:

    @Path(&quot;/orders&quot;)
    @Consumes(MediaType.APPLICATION_JSON)
    @Produces(MediaType.APPLICATION_JSON)
    public class OrderResource {
        
        private static Map&lt;Integer, Order&gt; orders = new HashMap&lt;Integer, Order&gt;();
    
        @POST
        public void createOrder(Order order) {
            
            orders.put(order.id, order);
        }
        
        @GET
        @Path(&quot;/{id}&quot;)
        public Order getOrder(@PathParam(&quot;id&quot;) int id) {
            Order order = orders.get(id);
            if (order == null) {
                order = new Order(0, &quot;Buy&quot;, &quot;Unknown&quot;, 0);
            }
            return order;
        }
    }

Here&#39;s the Order object:

    public class Order {
        public int id;
        public String side;
        public String symbol;
        public int quantity;
        ...
    }

A GET request like this works perfectly and returns an order in JSON format:

    GET http://localhost:8080/jaxrs-oms/rest/orders/123 HTTP/1.1

However a POST request like this returns a 415:

    POST http://localhost:8080/jaxrs-oms/rest/orders HTTP/1.1
    
    {
        &quot;id&quot;: &quot;123&quot;,
        &quot;symbol&quot;: &quot;AAPL&quot;,
        &quot;side&quot;: &quot;Buy&quot;,
        &quot;quantity&quot;: &quot;1000&quot;
    }

How to POST a JSON object to a JAX-RS service

I want to create an employee information in the system by uploading an image along with employee data. I am able to do it with different rest calls using jersey. But I want to achieve in one rest call.
I provide below the structure. Please help me how to do in this regard.


    @POST
	@Path(&quot;/upload2&quot;)
	@Consumes({MediaType.MULTIPART_FORM_DATA,MediaType.APPLICATION_XML, MediaType.APPLICATION_JSON})
	public Response uploadFileWithData(
			@FormDataParam(&quot;file&quot;) InputStream fileInputStream,
			@FormDataParam(&quot;file&quot;) FormDataContentDisposition contentDispositionHeader,
            Employee emp) {

    //..... business login
    
    }



Whenever I am trying to do, I get error in Chrome postman. The simple structure of my Employee json is given below.

    {
        &quot;Name&quot;: &quot;John&quot;,
        &quot;Age&quot;: 23,
        &quot;Email&quot;: &quot;john@gmail.com&quot;,
        &quot;Adrs&quot;: {
            &quot;DoorNo&quot;: &quot;12-A&quot;,
            &quot;Street&quot;: &quot;Street-11&quot;,
            &quot;City&quot;: &quot;Bangalore&quot;,
            &quot;Country&quot;: &quot;Karnataka&quot;
        }
    }

However I can do it by making two different call, but I want to achieve in one rest call so that I can receive the file as well as the actual data of the employee.

Request you to help in this regard.


File upload along with other object in Jersey restful web service

I am facing issues while consuming JAX-RS services as JSON.

Below I have added my code.

This is my service class:

    //Sets the path to base URL + /hello
    @Path(&quot;/hello&quot;) 
    @Consumes(MediaType.APPLICATION_JSON)
    @Produces(MediaType.APPLICATION_JSON)
    public class Hello {

	    @GET
    	@Produces(&quot;application/json&quot;)
    	public Student getStudent() {
		
	    	Student s = new Student();
		    s.first_name = &quot;Test First Name !!!&quot;;
    		s.last_name = &quot;Test Last Name!!!&quot;;
		
	    	return s;
	    }

`Student` class which I am trying to get from service:
  
    @XmlRootElement
    public class Student implements Serializable {
    	
    	public String first_name;
    	public String last_name;
    	
    	public String getFirst_name() {
    		return first_name;
    	}
    
    	public void setFirst_name(String first_name) {
    		this.first_name = first_name;
    	}
    
    	public String getLast_name() {
    		return last_name;
    	}
    
    	public void setLast_name(String last_name) {
    		this.last_name = last_name;
    	}
    
    	public Student()
    	{
    		first_name = &quot;Fahad&quot;;
    		last_name = &quot;Mullaji&quot;;
    	}
    }

Web XML on service side.

&lt;!-- language: lang-xml --&gt;

    &lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
    &lt;web-app xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
    	xmlns=&quot;http://java.sun.com/xml/ns/javaee&quot;
    	xsi:schemaLocation=&quot;http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd&quot;
    	id=&quot;WebApp_ID&quot; version=&quot;3.0&quot;&gt;
    	&lt;display-name&gt;com.vogella.jersey.first&lt;/display-name&gt;
    	&lt;servlet&gt;
    		&lt;servlet-name&gt;Jersey REST Service&lt;/servlet-name&gt;
    		&lt;servlet-class&gt;org.glassfish.jersey.servlet.ServletContainer&lt;/servlet-class&gt;
    		&lt;!-- Register resources and providers under com.vogella.jersey.first package. --&gt;
    		&lt;init-param&gt;
    			&lt;param-name&gt;jersey.config.server.provider.packages&lt;/param-name&gt;
    			&lt;param-value&gt;com.vogella.jersey.first&lt;/param-value&gt;
    		&lt;/init-param&gt;
    		&lt;init-param&gt;
    			&lt;param-name&gt;com.sun.jersey.api.json.POJOMappingFeature&lt;/param-name&gt;
    			&lt;param-value&gt;true&lt;/param-value&gt;
    		&lt;/init-param&gt;
    
    		&lt;load-on-startup&gt;1&lt;/load-on-startup&gt;
    	&lt;/servlet&gt;
    	&lt;servlet-mapping&gt;
    		&lt;servlet-name&gt;Jersey REST Service&lt;/servlet-name&gt;
    		&lt;url-pattern&gt;/rest/*&lt;/url-pattern&gt;
    	&lt;/servlet-mapping&gt;
    &lt;/web-app&gt; 

I don&#39;t know how to fix this issue.
I am using SOAP UI for testing JSON response but I guess that it should not matter.

Many places I read that I need to add the code below. But I don&#39;t know where. I am not using Maven for building.

    &lt;dependency&gt;
        &lt;groupId&gt;org.glassfish.jersey.media&lt;/groupId&gt;
        &lt;artifactId&gt;jersey-media-moxy&lt;/artifactId&gt;
    &lt;/dependency&gt;

Server is looking for function to parse `Student` object to JSON but it is not able to find function or jar file for it. 
I have added jar of Genson, Moxy, RESTEasy and Jackson but I think that&#39;s the problem.
I think I am missing mapping somewhere.

MessageBodyWriter not found for media type=application/json

I thought that the order of Maven dependencies doesn&#39;t matter before and regard this as a pro of it. And this is my old `pom.xml`&#39;s dependencies:

    &lt;dependencies&gt;

        &lt;dependency&gt;
            &lt;groupId&gt;org.glassfish.jersey.containers&lt;/groupId&gt;
            &lt;artifactId&gt;jersey-container-servlet&lt;/artifactId&gt;
            &lt;version&gt;2.19&lt;/version&gt;
        &lt;/dependency&gt;

        &lt;dependency&gt;
            &lt;groupId&gt;org.springframework&lt;/groupId&gt;
            &lt;artifactId&gt;spring-web&lt;/artifactId&gt;
            &lt;version&gt;4.1.7.RELEASE&lt;/version&gt;
        &lt;/dependency&gt;

        &lt;dependency&gt;
            &lt;groupId&gt;org.glassfish.jersey.ext&lt;/groupId&gt;
            &lt;artifactId&gt;jersey-spring3&lt;/artifactId&gt;
            &lt;version&gt;2.19&lt;/version&gt;
        &lt;/dependency&gt;

        &lt;dependency&gt;
            &lt;groupId&gt;org.glassfish.jersey.media&lt;/groupId&gt;
            &lt;artifactId&gt;jersey-media-moxy&lt;/artifactId&gt;
            &lt;version&gt;2.19&lt;/version&gt;
        &lt;/dependency&gt;

    &lt;/dependencies&gt;
It works well, and today I wanna move spring dependency to the bottom so that those jersey related can be together. However then I can no longer make it working, my Jetty complains:

    [ERROR] Failed to execute goal org.eclipse.jetty:jetty-maven-plugin:9.3.0.M1:run (default-cli) on project mtest: Execution default-cli of goal org.eclipse.jetty:jetty-maven-plugin:9.3.0.M1:run failed: A required class was missing while executing org.eclipse.jetty:jetty-maven-plugin:9.3.0.M1:run: org/apache/commons/logging/LogFactory
That is really confusing, so do I have to concern about dependencies order? How do I know the correct order?

Why order of Maven dependencies matter?

I&#39;m using the Jersey Client library to run tests against a rest service running on jboss.
I have https set up fine on the server (running on localhost), using a self signed cert. 

However whenever I run my tests with the https url I get the following error:

    com.sun.jersey.api.client.ClientHandlerException: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
    	at com.sun.jersey.client.urlconnection.URLConnectionClientHandler.handle(URLConnectionClientHandler.java:131)
    	at com.sun.jersey.api.client.Client.handle(Client.java:629)
    	at com.sun.jersey.oauth.client.OAuthClientFilter.handle(OAuthClientFilter.java:137)
    	at com.sun.jersey.api.client.WebResource.handle(WebResource.java:601)
    	at com.sun.jersey.api.client.WebResource.access$200(WebResource.java:74)
    	at com.sun.jersey.api.client.WebResource$Builder.get(WebResource.java:459)
    	at test.helper.Helper.sendSignedRequest(Helper.java:174)
    	... And so on

I know this is because my self signed cert is not in the java keystore. Is there any way I can make the `Client` not check the validity of the ssl cert and just use it regardless?

This code will only ever be run against test servers so I don&#39;t want to go to the hassle of adding new trusted certs each time we set up a new test server.

Here&#39;s the code which is making the call:

    OAuthParameters params = new OAuthParameters();
    		
    // baseline OAuth parameters for access to resource
    params.signatureMethod(props.getProperty(&quot;signature_method&quot;));
    params.consumerKey(props.getProperty(&quot;consumer_key&quot;));
    params.setToken(props.getProperty(&quot;token&quot;));
    params.setVersion(&quot;1.0&quot;);
    params.nonce();
    	
    // OAuth secrets to access resource
    OAuthSecrets secrets = new OAuthSecrets();
    secrets.consumerSecret(props.getProperty(&quot;consumer_secret&quot;));
    secrets.setTokenSecret(props.getProperty(&quot;token_secret&quot;));
    	
    // Jersey client to make REST calls to token services
    Client client = Client.create();
    	
    // OAuth test server resource
    WebResource resource = client.resource(props.getProperty(&quot;url&quot;));
    		
    // if parameters and secrets remain static, filter cab be added to each web resource
    OAuthClientFilter filter = new OAuthClientFilter(client.getProviders(), params, secrets);
    	
    // filter added at the web resource level
    resource.addFilter(filter);
    WebResource.Builder wbr = resource.getRequestBuilder().accept(props.getProperty(&quot;accept&quot;));
    		
    return wbr.get(ClientResponse.class);

Any help would be greatly appreciated.

Ignore self-signed ssl cert using Jersey Client

How can one get the full HTTP REST request body for a `POST` request using Jersey?

In our case the data will be XML.  Size would vary from 1K to 1MB.

The [docs][1] seem to indicate you should use `MessageBodyReader` but I can&#39;t see any examples.


  [1]: http://dlc.sun.com/pdf/820-4867/820-4867.pdf

How to get full REST request body using Jersey?

From what I can find online, the state of the art for Guice + Jersey integration has stagnated since 2008 when it appears both teams reached an impasse. The crux of the issue is that JAX-RS annotations perform field and method injection and this doesn&#39;t play nicely with Guice&#39;s own dependency injection.

A few examples which I&#39;ve found don&#39;t go far enough to elucidate:

* Iqbalyusuf&#39;s post on [Jersey + Guice on Google App Engine Java][1] suffers from a lot of boilerplate (manually getting and calling the injector). I want binding and injection should happen behind the scenes via Guice annotations.

* Jonathan Curran&#39;s article [Creating a RESTful service with Jersey, Guice, and JSR-250][2] gave me hope because it&#39;s much more current (2010), but went no further than showing how to start up a Jersey service inside of a Guice ServletModule. However, there are no examples of doing any real dependency injection. I suppose that was left as an exercise for the reader. Curran&#39;s post may in fact be the correct first step towards wiring up Guice and Jersey and so I plan on starting with that.

* tantalizingly [James Strachan writes][3]:
&gt; JAX-RS works well with dependency
&gt; injection frameworks such as Spring,
&gt; Guice, GuiceyFruit or JBossMC - you
&gt; can basically pick whichever one you
&gt; prefer.

  But I see no evidence that is true from a practitioner&#39;s point of view.


What I find lacking are practical examples and explanations on how to combine JAX-RS and Guice annotations. For instance:

* I believe I cannot use constructor injection with any resource as Jersey wants to control this
* I&#39;m uncertain whether I can combine @Inject with @PathParam, @QueryParam, et al.
* How to use injection in a MessageBodyWriter implementation

Does anyone have examples, preferably with source, of non-trivial application which combines Jersey and Guice without sacrificing one or the other in the process? I&#39;m keeping on this road regardless, but the bits and pieces on the Jersey and Guice lists makes me think I&#39;m repeating the work of others who came before me.

  [1]: http://blog.iparissa.com/jersey-guice-on-google-app-engine-java/
  [2]: http://blog.curran.in/2010/02/creating-restful-service-with-jersey.html
  [3]: http://macstrac.blogspot.com/2009/01/jax-rs-as-one-web-framework-to-rule.html

Practical advice on using Jersey and Guice for RESTful service

I&#39;m trying to minimize repeated code for a number of JAX-RS resource handlers, all of which require a few of the same path and query parameters. The basic url template for each resource looks like this:

    /{id}/resourceName
    
and each resource has multiple subresources:

    /{id}/resourceName/subresourceName

So, resource/subresource paths (incl. query parameters) might look like

    /12345/foo/bar?xyz=0
    /12345/foo/baz?xyz=0
    /12345/quux/abc?xyz=0
    /12345/quux/def?xyz=0
    
The common parts across resources `foo` and `quux` are `@PathParam(&quot;id&quot;)` and `@QueryParam(&quot;xyz&quot;)`. I *could* implement the resource classes like this:

    // FooService.java
    @Path(&quot;/{id}/foo&quot;)
    public class FooService
    {
        @PathParam(&quot;id&quot;) String id;
        @QueryParam(&quot;xyz&quot;) String xyz;
        
        @GET @Path(&quot;bar&quot;)
        public Response getBar() { /* snip */ }
        
        @GET @Path(&quot;baz&quot;)
        public Response getBaz() { /* snip */ }
    }

&lt;!--&gt;

    // QuuxService.java
    @Path(&quot;/{id}/quux&quot;)
    public class QuxxService
    {
        @PathParam(&quot;id&quot;) String id;
        @QueryParam(&quot;xyz&quot;) String xyz;
        
        @GET @Path(&quot;abc&quot;)
        public Response getAbc() { /* snip */ }
        
        @GET @Path(&quot;def&quot;)
        public Response getDef() { /* snip */ }
    }
    
I&#39;ve managed to avoid repeating the parameter injection into every single `get*` method.&lt;sup&gt;1&lt;/sup&gt;  This is a good start, but I&#39;d like to be able to avoid the repetition across resource classes as well. An approach that works with CDI (which I also need) is to use an `abstract` base class which `FooService` and `QuuxService` could `extend`:

    // BaseService.java
    public abstract class BaseService
    {
        // JAX-RS injected fields
        @PathParam(&quot;id&quot;) protected String id;
        @QueryParam(&quot;xyz&quot;) protected String xyz;
        
        // CDI injected fields
        @Inject protected SomeUtility util;
    }

&lt;!--&gt;
    
    // FooService.java
    @Path(&quot;/{id}/foo&quot;)
    public class FooService extends BaseService
    {
        @GET @Path(&quot;bar&quot;)
        public Response getBar() { /* snip */ }
        
        @GET @Path(&quot;baz&quot;)
        public Response getBaz() { /* snip */ }
    }

&lt;!--&gt;
    
    // QuuxService.java
    @Path(&quot;/{id}/quux&quot;)
    public class QuxxService extends BaseService
    {   
        @GET @Path(&quot;abc&quot;)
        public Response getAbc() { /* snip */ }
        
        @GET @Path(&quot;def&quot;)
        public Response getDef() { /* snip */ }
    }
    
Inside of the `get*` methods, the CDI injection (miraculously) works correctly: the `util` field is not null. Unfortunately, the JAX-RS injection does _not_ work; `id` and `xyz` are `null` in the `get*` methods of `FooService` and `QuuxService`.

### Is there a fix or workaround for this problem?

Given that the CDI works as I&#39;d like it to, I&#39;m wondering if the failure to inject `@PathParam`s (etc.) into subclasses is a bug or just part of the JAX-RS spec.


----------


Another approach I have already tried is using `BaseService` as a single point of entry that delegates to `FooService` and `QuuxService` as needed. This is basically as described in [RESTful Java with JAX-RS][1] using subresource locators.

    // BaseService.java
    @Path(&quot;{id}&quot;)
    public class BaseService
    {
        @PathParam(&quot;id&quot;) protected String id;
        @QueryParam(&quot;xyz&quot;) protected String xyz;
        @Inject protected SomeUtility util;
        
        public BaseService () {} // default ctor for JAX-RS
        
        // ctor for manual &quot;injection&quot;
        public BaseService(String id, String xyz, SomeUtility util)
        {
            this.id = id;
            this.xyz = xyz;
            this.util = util;
        }
        
        @Path(&quot;foo&quot;)
        public FooService foo()
        {
            return new FooService(id, xyz, util); // manual DI is ugly
        }
        
        @Path(&quot;quux&quot;)
        public QuuxService quux()
        {
            return new QuuxService(id, xyz, util); // yep, still ugly
        }
    }

&lt;!--&gt;
    
    // FooService.java
    public class FooService extends BaseService
    {
        public FooService(String id, String xyz, SomeUtility util)
        {
            super(id, xyz, util); // the manual DI ugliness continues
        }
        
        @GET @Path(&quot;bar&quot;)
        public Response getBar() { /* snip */ }
        
        @GET @Path(&quot;baz&quot;)
        public Response getBaz() { /* snip */ }
    }

&lt;!--&gt;
    
    // QuuxService.java
    public class QuuzService extends BaseService
    {
        public FooService(String id, String xyz, SomeUtility util)
        {
            super(id, xyz, util); // the manual DI ugliness continues
        }
        
        @GET @Path(&quot;abc&quot;)
        public Response getAbc() { /* snip */ }
        
        @GET @Path(&quot;def&quot;)
        public Response getDef() { /* snip */ }
    }

The downside to this approach is that neither CDI injection nor JAX-RS injection works in the subresource classes. The reason for this is fairly obvious&lt;sup&gt;2&lt;/sup&gt;, but what that *means* is that I have to manually re-inject the fields into the subclasses&#39; constructor, which is messy, ugly, and doesn&#39;t easily let me customize further injection. Example: say I wanted to `@Inject` an instance into `FooService` but not `QuuxService`. Because I&#39;m explicitly instantiating the subclasses of `BaseService`, CDI injection won&#39;t work, so the ugliness is continued.

----------

## tl;dr What&#39;s the right way to avoid repeatedly injecting fields across JAX-RS resource handler classes?

### And why aren&#39;t inherited fields injected by JAX-RS, while CDI has no issues with this?

----------

# Edit 1
With a bit of direction from [@Tarlog][2], I think I&#39;ve found the answer to one of my questions,

&gt; Why aren&#39;t inherited fields injected by JAX-RS?

In [JSR-311 &#167;3.6][3]:

&gt; If a subclass or implementation method has any JAX-RS annotations then *all* of the annotations on the super class or interface method are ignored.

I&#39;m sure that there&#39;s a real reason for this decision, but unfortunately that fact is working against me in this particular use case. I&#39;m still interested in any possible workarounds.

----------


&lt;sub&gt;&lt;sup&gt;1&lt;/sup&gt; The caveat with using field-level injection is that I&#39;m now tied to per-request resource class instantiation, but I can live with that.&lt;/sub&gt;  
&lt;sub&gt;&lt;sup&gt;2&lt;/sup&gt; Because I&#39;m the one calling `new FooService()` rather than the container/the JAX-RS implementation.&lt;/sub&gt;  


  [1]: http://books.google.com/books?id=_jQtCL5_vAcC&amp;lpg=PP1&amp;dq=restful%20java%20with%20jax-rs&amp;pg=PA52#v=onepage&amp;q&amp;f=false
  [2]: https://stackoverflow.com/users/547779/tarlog
  [3]: http://jsr311.java.net/nonav/releases/1.1/spec/spec3.html#x3-330003.6

Staying DRY with JAX-RS

I have written a pretty extensive REST API using Java Jersey (and JAXB). I have also written the documentation using a Wiki, but its been a totally manual process, which is very error-prone, especially when we need to make modifications, people tend to forget to update the wiki.

From looking around, most other REST API&#39;s are also manually creating their documentation. But I&#39;m wondering if theres maybe a good solution to this.

The kind of things which need to be documented for each endpoint are:

 - Service Name  
 - Category
 - URI 
 - Parameter
 - Parameter Types
 - Response Types
 - Response Type Schema (XSD) 
 - Sample requests and responses
 - Request type (Get/Put/Post/Delete) 
 - Description
 - Error codes which may be returned


And then of course there are some general things which are global such as

 - Security
 - Overview of REST
 - Error handling
 - Etc


These general things are fine to describe once and don&#39;t need to be automated, but for the web service methods themselves it seems highly desirable to automate it. 

I&#39;ve thought of maybe using annotations, and writing a small program which generates XML, and then an XSLT which should generate the actual documentation in HTML. Does it make more sense to use custom XDoclet?


How to automate documentation of a REST API (Jersey Implementation)

I have a requirement for RESTFul webservices. It is up to my team to decide whether to go with Jersey or Restlet or RESTEasy or anything else. after omitting other frameworks, we are not able to choose between RESTEasy and Jersey.

Since both of them seem to be almost the same, what should we consider?
 
The client API should be simple and rich. We are already using JBoss 5.1 in production.

Please let me know the pros and cons of Jersey and RESTEasy. Except that it is from JBoss, I&#39;m not able to find any valid point over Jersey.

RESTEasy or Jersey?

In a Java method, I&#39;d like to use a Jersey client object to do a POST operation on a RESTful web service (also written using Jersey) but am not sure how to use the client to send the values that will be used as FormParam&#39;s on the server.  I&#39;m able to send query params just fine.



Using the Jersey client to do a POST operation

I have a web server running with Jersey REST resources up and I wonder how to get an image/png reference for the browsers img tag; after submitting a Form or getting an Ajax response. The image processing code for adding graphics is working, just need to return it somehow.

Code:

    @POST
    @Path(&quot;{fullsize}&quot;)
    @Consumes(MediaType.MULTIPART_FORM_DATA)
    @Produces(&quot;image/png&quot;)
    // Would need to replace void
    public void getFullImage(@FormDataParam(&quot;photo&quot;) InputStream imageIS,
                             @FormDataParam(&quot;submit&quot;) String extra) {

          BufferedImage image = ImageIO.read(imageIS);

          // .... image processing
          //.... image processing

          return ImageIO.  ..  ?

    }


Cheers

How to return a PNG image from Jersey REST service method to the browser

I am using Jersey based restful Service implementation strategy to build a service which will be used to upload files.
My service class name is : UploadFileService.java (See Code below)

     package com.jerser.service;
    
    import java.io.File;
    import java.io.FileOutputStream;
    import java.io.IOException;
    import java.io.InputStream;
    import java.io.OutputStream;
    import javax.ws.rs.Consumes;
    import javax.ws.rs.POST;
    import javax.ws.rs.Path;
    import javax.ws.rs.core.MediaType;
    import javax.ws.rs.core.Response;
    import com.sun.jersey.core.header.FormDataContentDisposition;
    import com.sun.jersey.multipart.FormDataParam;
    
    @Path(&quot;/fileUpload&quot;)
    public class UploadFileService {
    
    	@POST
    	@Path(&quot;/upload&quot;)
    	@Consumes(MediaType.MULTIPART_FORM_DATA)
    	public Response uploadFile(
    		@FormDataParam(&quot;file&quot;) InputStream uploadedInputStream,
    		@FormDataParam(&quot;file&quot;) FormDataContentDisposition fileDetail) {
     
    		String uploadedFileLocation = &quot;d://uploaded/&quot; + fileDetail.getFileName();
     
    		// save it
    		writeToFile(uploadedInputStream, uploadedFileLocation);
     
    		String output = &quot;File uploaded to : &quot; + uploadedFileLocation;
     
    		return Response.status(200).entity(output).build();
     
    	}
     
    	// save uploaded file to new location
    	private void writeToFile(InputStream uploadedInputStream,
    		String uploadedFileLocation) {
     
    		try {
    			OutputStream out = new FileOutputStream(new File(
    					uploadedFileLocation));
    			int read = 0;
    			byte[] bytes = new byte[1024];
     
    			out = new FileOutputStream(new File(uploadedFileLocation));
    			while ((read = uploadedInputStream.read(bytes)) != -1) {
    				out.write(bytes, 0, read);
    			}
    			out.flush();
    			out.close();
    		} catch (IOException e) {
     
    			e.printStackTrace();
    		}
     
    	}
    	
    }

These are the JAR files I have inside my lib:

&gt;     aopalliance-repackaged-2.4.0-b10.jar     
&gt;     asm-debug-all-5.0.2.jar     
&gt;     hk2-api-2.4.0-b10.jar  
&gt;     hk2-locator-2.4.0-b10.jar     
&gt;     hk2-utils-2.4.0-b10.jar     
&gt;     javassist-3.18.1-GA.jar     
&gt;     javax.annotation-api-1.2.jar     
&gt;     javax.inject-2.4.0-b10.jar     
&gt;     javax.servlet-api-3.0.1.jar     
&gt;     javax.ws.rs-api-2.0.1.jar     
&gt;     jaxb-api-2.2.7.jar     
&gt;     jersey-client.jar     
&gt;     jersey-common.jar     
&gt;     jersey-container-servlet-core.jar     
&gt;     jersey-container-servlet.jar     
&gt;     jersey-core-1.11.jar     
&gt;     jersey-guava-2.17.jar     
&gt;     jersey-media-jaxb.jar  
&gt;     jersey-multipart-1.18.jar    
&gt;     jersey-server.jar
&gt;     org.osgi.core-4.2.0.jar
&gt;     osgi-resource-locator-1.0.1.jar     
&gt;     persistence-api-1.0.jar    
&gt;     validation-api-1.1.0.Final.jar

I am getting the following error when I am trying to up my tomcat server :

    org.glassfish.jersey.server.model.ModelValidationException: Validation of the application resource model has failed during application initialization.
    [[FATAL] No injection source found for a parameter of type public javax.ws.rs.core.Response com.jerser.service.UploadFileService.uploadFile(java.io.InputStream,com.sun.jersey.core.header.FormDataContentDisposition) at index 0.; source=&#39;ResourceMethod{httpMethod=POST, consumedTypes=[multipart/form-data], producedTypes=[], suspended=false, suspendTimeout=0, suspendTimeoutUnit=MILLISECONDS, invocable=Invocable{handler=ClassBasedMethodHandler{handlerClass=class com.jerser.service.UploadFileService, handlerConstructors=[org.glassfish.jersey.server.model.HandlerConstructor@d3e2d4]}, definitionMethod=public javax.ws.rs.core.Response com.jerser.service.UploadFileService.uploadFile(java.io.InputStream,com.sun.jersey.core.header.FormDataContentDisposition), parameters=[Parameter [type=class java.io.InputStream, source=file, defaultValue=null], Parameter [type=class com.sun.jersey.core.header.FormDataContentDisposition, source=file, defaultValue=null]], responseType=class javax.ws.rs.core.Response}, nameBindings=[]}&#39;]
    	at org.glassfish.jersey.server.ApplicationHandler.initialize(ApplicationHandler.java:528)
    	at org.glassfish.jersey.server.ApplicationHandler.access$500(ApplicationHandler.java:166)
    	at org.glassfish.jersey.server.ApplicationHandler$3.run(ApplicationHandler.java:327)
    	at org.glassfish.jersey.internal.Errors$2.call(Errors.java:289)
    	at org.glassfish.jersey.internal.Errors$2.call(Errors.java:286)
    	at org.glassfish.jersey.internal.Errors.process(Errors.java:315)
    	at org.glassfish.jersey.internal.Errors.process(Errors.java:297)
    	at org.glassfish.jersey.internal.Errors.processWithException(Errors.java:286)
    	at org.glassfish.jersey.server.ApplicationHandler.&lt;init&gt;(ApplicationHandler.java:324)
    	at org.glassfish.jersey.servlet.WebComponent.&lt;init&gt;(WebComponent.java:338)
    	at org.glassfish.jersey.servlet.ServletContainer.init(ServletContainer.java:171)
    	at org.glassfish.jersey.servlet.ServletContainer.init(ServletContainer.java:363)
    	at javax.servlet.GenericServlet.init(GenericServlet.java:160)
    	at org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1176)
    	at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1102)
    	at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1009)
    	at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4885)
    	at org.apache.catalina.core.StandardContext$3.call(StandardContext.java:5212)
    	at org.apache.catalina.core.StandardContext$3.call(StandardContext.java:5207)
    	at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
    	at java.util.concurrent.FutureTask.run(Unknown Source)
    	at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
    	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
    	at java.lang.Thread.run(Unknown Source)


Over the internet I found there are plenty of example which shows How to upload MULTIPART file using RESTFul API. But with same solution. I am not able to run those code as well.
I think I am doing something wrong with the JAR files. Could anyone please help me on this?

MULTIPART_FORM_DATA: No injection source found for a parameter of type public javax.ws.rs.core.Response

In jersey 1 we had a function [setConnectTimeout][1] in the class `com.sun.jersey.api.client.Client`.


In jersey 2 the `javax.ws.rs.client.Client` class is used where this function is missing.

How to set connection timeout and read timeout in jersey 2.x?


  [1]: https://jersey.java.net/apidocs/1.1.5/jersey/com/sun/jersey/api/client/Client.html#setConnectTimeout%28java.lang.Integer%29

How to set the connection and read timeout with Jersey 2.x?

I want to build a RESTful service/API. I used some framework like play to build it but I want to try other more efficient ways. I heard that Jersey is a common library for building a REST API, and Spring is also a good framework. But I also saw some solutions like Spring+Jersey. Thus, I am a little confused about those REST API solutions. 

Can anyone tell me what is the difference among those? Jersey REST, Spring REST and Spring+Jersey REST? 

My goal is building a couple of REST APIs that take JSON as input/output. I have jar file as the backend process logic to process the input a JSON/object and return a JSON/object.

What is the difference between Spring REST service, Jersey REST service and Spring+Jersey solutions?

I&#39;m using Jersey to create a REST web service for a server component.

The JAXB-annotated object I want to serialize in a list looks like this:

    @XmlRootElement(name = &quot;distribution&quot;)
    @XmlType(name = &quot;tDistribution&quot;, propOrder = {
        &quot;id&quot;, &quot;name&quot;
    })
    public class XMLDistribution {
        private String id;
        private String name;
        // no-args constructor, getters, setters, etc
    }

I have a REST resource to retrieve one distribution which looks like this:

    @Path(&quot;/distribution/{id: [1-9][0-9]*}&quot;)
    public class RESTDistribution {
        @GET
        @Produces(&quot;application/json&quot;)
        public XMLDistribution retrieve(@PathParam(&quot;id&quot;) String id) {
            return retrieveDistribution(Long.parseLong(id));
        }
        // business logic (retrieveDistribution(long))
    }

I also have a REST resource to retrieve a list of all distributions, which looks like this:

    @Path(&quot;/distributions&quot;)
    public class RESTDistributions {
        @GET
        @Produces(&quot;application/json&quot;)
        public List&lt;XMLDistribution&gt; retrieveAll() {
            return retrieveDistributions();
        }
        // business logic (retrieveDistributions())
    }

I use a ContextResolver to customize JAXB serialization, which is currently configured like this:

    @Provider
    @Produces(&quot;application/json&quot;)
    public class JAXBJSONContextResolver implements ContextResolver&lt;JAXBContext&gt; {
        private JAXBContext context;
        public JAXBJSONContextResolver() throws Exception {
            JSONConfiguration.MappedBuilder b = JSONConfiguration.mapped();
            b.nonStrings(&quot;id&quot;);
            b.rootUnwrapping(true);
            b.arrays(&quot;distribution&quot;);
            context = new JSONJAXBContext(b.build(), XMLDistribution.class);
        }
        @Override
        public JAXBContext getContext(Class&lt;?&gt; objectType) {
            return context;
        }
    }

Both REST resources work, as well as the context resolver. This is an example of output for the first one:

```
// path: /distribution/1
{
  &quot;id&quot;: 1,
  &quot;name&quot;: &quot;Example Distribution&quot;
}
```

Which is exactly what I want. This is an example of output for the list:

```
// path: /distributions
{
  &quot;distribution&quot;: [{
    &quot;id&quot;: 1,
    &quot;name&quot;: &quot;Sample Distribution 1&quot;
  }, {
    &quot;id&quot;: 2,
    &quot;name&quot;: &quot;Sample Distribution 2&quot;
  }]
}
```

Which is not quite what I want.

I don&#39;t understand why there is an enclosing &lt;code&gt;distribution&lt;/code&gt; tag there. I wanted to remove it with &lt;code&gt;.rootUnwrapping(true)&lt;/code&gt; in the context resolver, but apparently that only removes another enclosing tag. This is the output with &lt;code&gt;.rootUnwrapping(false)&lt;/code&gt;:

```
// path: /distribution/1
{
  &quot;distribution&quot;: {
    &quot;id&quot;: 1,
    &quot;name&quot;: &quot;Example Distribution&quot;
  }
} // not ok
// path: /distributions
{
  &quot;xMLDistributions&quot;: {
    &quot;distribution&quot;: [{
      &quot;id&quot;: 1,
      &quot;name&quot;: &quot;Sample Distribution 1&quot;
    }, {
      &quot;id&quot;: 2,
      &quot;name&quot;: &quot;Sample Distribution 2&quot;
    }]
  }
}
```

I also had to configure &lt;code&gt;.arrays(&quot;distribution&quot;)&lt;/code&gt; to always get a JSON array, even with only one element.

Ideally, I&#39;d like to have this as an output:

```
// path: /distribution/1
{
  &quot;id&quot;: 1,
  &quot;name&quot;: &quot;Example Distribution&quot;
} // currently works
// path: /distributions
[{
  &quot;id&quot;: 1,
  &quot;name&quot;: &quot;Sample Distribution 1&quot;
}, {
  &quot;id&quot;: 2,
  &quot;name&quot;: &quot;Sample Distribution 2&quot;
}]
```

I tried to return a &lt;code&gt;List&amp;lt;XMLDistribution&amp;gt;&lt;/code&gt;, a &lt;code&gt;XMLDistributionList&lt;/code&gt; (wrapper around a list), a &lt;code&gt;XMLDistribution[]&lt;/code&gt;, but I couldn&#39;t find a way to get a simple JSON array of distributions in my required format.

I also tried the other notations returned by &lt;code&gt;JSONConfiguration.natural()&lt;/code&gt;, &lt;code&gt;JSONConfiguration.mappedJettison()&lt;/code&gt;, etc, and couldn&#39;t get anything resembling what I need.

Does anyone know if it is possible to configure JAXB to do this?

How can I customize serialization of a list of JAXB objects to JSON?

I have been working on a REST web service using Jersey for a few days now, and managed to have all CRUD operations working, with several exchange formats: XML, JSON, Google Protobuf.

However I am facing some issues related to automatically generated WADL and XSD.

----------

#Context

To define the objects exchanged in these three formats, I have followed a **&quot;contract-first&quot; approach**:

 - from a XSD I wrote, I generated my model classes using JAXB;
 - from an equivalent proto file I wrote, I generated the Google Protobuf classes (and internally have a way to convert these to the JAXB-generated objects, in order to have one unique model).

However, as I would like my users to be able to **generate their classes** too, I would like to share these schema files (.xsd and .proto) and have them **well integrated with the automatically generated WADL**.

For that purpose, thanks to [this][1] wiki page:

 - I have exposed the two files under
  - `/schema/schema.xsd`
  - `/schema/schema.proto`
 - I have added an application-grammar file:

        &lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot; standalone=&quot;yes&quot;?&gt;
        &lt;grammars xmlns=&quot;http://wadl.dev.java.net/2009/02&quot; 
                  xmlns:xsd=&quot;http://www.w3.org/2001/XMLSchema&quot;
                  xmlns:xi=&quot;http://www.w3.org/1999/XML/xinclude&quot;&gt;
            &lt;include href=&quot;../schema/schema.xsd&quot; /&gt;
        &lt;/grammars&gt;

 - I have added a customized WADL generator:

         public class RichWadlGeneratorConfig extends WadlGeneratorConfig {
            @Override
            public List&lt;WadlGeneratorDescription&gt; configure() {
                return generator(WadlGeneratorApplicationDoc.class)
                    .prop(&quot;applicationDocsStream&quot;, &quot;application-doc.xml&quot;)
                    .generator(WadlGeneratorGrammarsSupport.class)
                    .prop(&quot;grammarsStream&quot;, &quot;application-grammars.xml&quot;)
                    .descriptions();
            }
         }

This way the below appears in the WADL, when I hit `/rest/application.wadl`:

    &lt;grammars&gt;
         &lt;include href=&quot;../schema/schema.xsd&quot;/&gt;
         &lt;include href=&quot;application.wadl/xsd0.xsd&quot;&gt;
              &lt;doc title=&quot;Generated&quot; xml:lang=&quot;en&quot;/&gt;
         &lt;/include&gt;
    &lt;/grammars&gt;

----------
 
#Problem

`/rest/application.wadl/xsd0.xsd` is automatically generated from my classes, but is quite **different** from what I initially had in `schema.xsd`.
In addition to that, calling a tool like `wadl2java` on this WADL fails miserably, presumably because

 - `/schema/schema.xsd`, and
 - `/rest/application.wadl/xsd0.xsd`

are now conflicting (two definitions for the same objects).

----------

#Questions

 1. Is there a way to disable the generation and diffusion of this automatically generated XSD? 
    (As I don&#39;t need it since I&#39;m following this &quot;contract-first&quot; approach)

 2. If not, is there a way to &quot;override&quot; its content with my manually written XSD when `/rest/application.wadl/xsd0.xsd` is hit?
    (I have googled around and found about WadlResource, to generate customized WADL, but found nothing about the XSD generation itself)

----------

Thanks in advance for your help!

M.

----------

#Edit

1) I raised the issue to the Jersey team and got a reply:
[http://java.net/projects/jersey/lists/users/archive/2012-06/message/8][2]

2) I raised a ticket (JERSEY-1230), according to Pavel&#39;s instructions.
I am currently following up to either submit a fix myself or get a fix from the Jersey team.


  [1]: https://wikis.oracle.com/display/Jersey/HowToConfigureExtendedWADL
  [2]: http://java.net/projects/jersey/lists/users/archive/2012-06/message/8

Troubles with WADL / generated XSD using Jersey with a contract-first approach

A service class has a `@GET` operation that accepts multiple parameters. These parameters are passed in as query parameters to the `@GET` service call.

	@GET
	@Path(&quot;find&quot;)
	@Produces(MediaType.APPLICATION_XML)
	public FindResponse find(@QueryParam(&quot;prop1&quot;) String prop1, 
                             @QueryParam(&quot;prop2&quot;) String prop2, 
                             @QueryParam(&quot;prop3&quot;) String prop3, 
                             @QueryParam(&quot;prop4&quot;) String prop4, ...) 

The list of these parameters are growing, so I would like to place them into a single bean that contains all these parameters.

    @GET
    @Path(&quot;find&quot;)
    @Produces(MediaType.APPLICATION_XML)
    public FindResponse find(ParameterBean paramBean) 
    {
        String prop1 = paramBean.getProp1();
        String prop2 = paramBean.getProp2();
        String prop3 = paramBean.getProp3();
        String prop4 = paramBean.getProp4();
    }

How would you do this?  Is this even possible?  

 



How do you map multiple query parameters to the fields of a bean on Jersey GET request?

I have been getting a ClassNotFoundException with `org.glassfish.jersey.servlet.ServletContainer` but it peculiarly started last night when I tried to start/re-start my Tomcat server (v7) with Eclipse Juno. 

Not sure what is going on. What&#39;s bizarre is that it just started happening last night while it was working perfectly well before that.

Here is the stacktrace:

    Feb 25, 2014 11:11:19 AM org.apache.catalina.core.ApplicationContext log
    INFO: Marking servlet com.att.ucomm.admin.UCommAdminFunctions as unavailable
    Feb 25, 2014 11:11:19 AM org.apache.catalina.core.StandardContext loadOnStartup
    SEVERE: Servlet /UCommAdminFunctions threw load() exception
    java.lang.ClassNotFoundException: org.glassfish.jersey.servlet.ServletContainer
    at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1671)
    at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1516)
    at org.apache.catalina.core.DefaultInstanceManager.loadClass(DefaultInstanceManager.java:415)
    at org.apache.catalina.core.DefaultInstanceManager.loadClassMaybePrivileged(DefaultInstanceManager.java:397)
    at org.apache.catalina.core.DefaultInstanceManager.newInstance(DefaultInstanceManager.java:118    )
    at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1048)
    at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:996)
    at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4762)
    at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5045)
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:140)
    at org.apache.catalina.core.StandardContext.reload(StandardContext.java:3670)
    at org.apache.catalina.loader.WebappLoader.backgroundProcess(WebappLoader.java:424)
    at org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1207)
    at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1393)
    at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1403)
    at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1403)
    at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1382)
    at java.lang.Thread.run(Unknown Source)

    Feb 25, 2014 11:11:19 AM org.apache.catalina.core.StandardContext reload
    INFO: Reloading Context with name [/UCommAdminFunctions] is completed
    Feb 25, 2014 11:13:33 AM org.apache.catalina.core.StandardWrapperValve invoke
    INFO: Servlet com.att.ucomm.admin.UCommAdminFunctions is currently unavailable

Here is my web.xml

&lt;!-- language: lang-xml --&gt;

    &lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
    &lt;web-app version=&quot;2.5&quot;
        xmlns=&quot;http://java.sun.com/xml/ns/javaee&quot;
        xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
        xsi:schemaLocation=&quot;http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd&quot;&gt;
 
    &lt;servlet&gt;
        &lt;servlet-name&gt;com.att.ucomm.admin.UCommAdminFunctions&lt;/servlet-name&gt;
        &lt;servlet-class&gt;org.glassfish.jersey.servlet.ServletContainer&lt;/servlet-class&gt;
 
        &lt;!-- Register JAX-RS Application, if needed. --&gt;
        &lt;init-param&gt;
            &lt;param-name&gt;com.att.ucomm.admin.UCommAdminFunctions&lt;/param-name&gt;
            &lt;param-value&gt;my.package.MyApplication&lt;/param-value&gt;
        &lt;/init-param&gt;
 
        &lt;!-- Register resources and providers under my.package. --&gt;
        &lt;init-param&gt;
            &lt;param-name&gt;jersey.config.server.provider.packages&lt;/param-name&gt;
            &lt;param-value&gt;com.att.ucomm.admin&lt;/param-value&gt;
        &lt;/init-param&gt;
 
        &lt;!-- Register my custom provider (not needed if it&#39;s in my.package) AND LoggingFilter. --&gt;
        &lt;init-param&gt;
            &lt;param-name&gt;jersey.config.server.provider.classnames&lt;/param-name&gt;
            &lt;param-value&gt;com.att.ucomm.admin.SecurityRequestFilter;org.glassfish.jersey.filter.LoggingFilter&lt;/param-value&gt;
        &lt;/init-param&gt;
 
        &lt;!-- Enable Tracing support. --&gt;
        &lt;init-param&gt;
            &lt;param-name&gt;jersey.config.server.tracing&lt;/param-name&gt;
            &lt;param-value&gt;ALL&lt;/param-value&gt;
        &lt;/init-param&gt;
 
        &lt;load-on-startup&gt;1&lt;/load-on-startup&gt;
    &lt;/servlet&gt;
 
    &lt;servlet-mapping&gt;
        &lt;servlet-name&gt;com.att.ucomm.admin.UCommAdminFunctions&lt;/servlet-name&gt;
        &lt;url-pattern&gt;/rest/*&lt;/url-pattern&gt;
    &lt;/servlet-mapping&gt;
    &lt;welcome-file-list&gt;
        &lt;welcome-file&gt;index.html&lt;/welcome-file&gt;
        &lt;welcome-file&gt;index.htm&lt;/welcome-file&gt;
        &lt;welcome-file&gt;index.jsp&lt;/welcome-file&gt;
        &lt;welcome-file&gt;default.html&lt;/welcome-file&gt;
        &lt;welcome-file&gt;default.htm&lt;/welcome-file&gt;
        &lt;welcome-file&gt;default.jsp&lt;/welcome-file&gt;
    &lt;/welcome-file-list&gt;
    &lt;/web-app&gt;

I made sure that the jar files for jersey were still there in WEB-INF/lib:

![WEB-INF/lib with jersey jars][1]


  [1]: http://i.stack.imgur.com/TgHjk.png

org.glassfish.jersey.servlet.ServletContainer ClassNotFoundException

I am struggling with a REST application with Grizzly, Jersey and Jackson, because Jersey ignores my custom ObjectMapper.

POM dependencies:

&lt;!-- language: xml --&gt;

	&lt;dependencies&gt;
		&lt;dependency&gt;
			&lt;groupId&gt;org.glassfish.jersey.containers&lt;/groupId&gt;
			&lt;artifactId&gt;jersey-container-grizzly2-servlet&lt;/artifactId&gt;
			&lt;version&gt;2.2&lt;/version&gt;
		&lt;/dependency&gt;
		&lt;dependency&gt;
			&lt;groupId&gt;com.fasterxml.jackson.jaxrs&lt;/groupId&gt;
			&lt;artifactId&gt;jackson-jaxrs-json-provider&lt;/artifactId&gt;
			&lt;version&gt;2.1.4&lt;/version&gt;
		&lt;/dependency&gt;
	&lt;/dependencies&gt;

Resulting versions are: Grizzly 2.3.3, Jackson 2.1.4 and Jersey 2.2.

Main class (I want explicit registration of Jersey components):

&lt;!-- language: java --&gt;

	public class Main {
		public static void main(String[] args) {
			try {
				ResourceConfig rc = new ResourceConfig();
				rc.register(ExampleResource.class);
				rc.register(ObjectMapperResolver.class);
	
				HttpHandler handler = ContainerFactory.createContainer(
						GrizzlyHttpContainer.class, rc);
	
				URI uri = new URI(&quot;http://0.0.0.0:8080/&quot;);
	
				HttpServer server = GrizzlyHttpServerFactory.createHttpServer(uri);
	
				ServerConfiguration config = server.getServerConfiguration();
				config.addHttpHandler(handler, &quot;/&quot;);
	
				server.start();
				System.in.read();
	
			} catch (ProcessingException | URISyntaxException | IOException e) {
				throw new Error(&quot;Unable to create HTTP server.&quot;, e);
			}
		}
	}

ContextResolver for ObjectMapper:


&lt;!-- language: java --&gt;

	@Provider
	@Produces(MediaType.APPLICATION_JSON)
	public class ObjectMapperResolver implements ContextResolver&lt;ObjectMapper&gt; {
	
		private final ObjectMapper mapper;
	
		public ObjectMapperResolver() {
			System.out.println(&quot;new ObjectMapperResolver()&quot;);
			mapper = new ObjectMapper();
			mapper.enable(SerializationFeature.INDENT_OUTPUT);
		}
	
		@Override
		public ObjectMapper getContext(Class&lt;?&gt; type) {
			System.out.println(&quot;ObjectMapperResolver.getContext(...)&quot;);
			return mapper;
		}
	
	}

Neither `ObjectMapperResolver` constructor nor `getContext` get called. What am I missing? I would prefer to use Jersey 2.2 and Jackson 2.1, because it is a dependency for another lib.

A full example can be found on GitHub: https://github.com/svenwltr/example-grizzly-jersey-jackson/tree/stackoverflow

All Jersey Solutions on Gang of Coders

Total of 45 Jersey Solutions