I&#39;m looking for a way to enable token-based authentication in Jersey. I am trying not to use any particular framework. Is that possible?

My plan is: A user signs up for my web service, my web service generates a token, sends it to the client, and the client will retain it. Then the client, for each request, will send the token instead of username and password.

I was thinking of using a custom filter for each request and `@PreAuthorize(&quot;hasRole(&#39;ROLE&#39;)&quot;)`, but I just thought that this causes a lot of requests to the database to check if the token is valid.

Or not create filter and in each request put a param token? So that each API first checks the token and after executes something to retrieve resource.

How to implement REST token-based authentication with JAX-RS and Jersey

I am not asking the question that is already asked here:
https://stackoverflow.com/questions/5579744/what-is-the-difference-between-pathparam-and-queryparam

This is a &quot;best practices&quot; or convention question.

When would you use `@PathParam` vs `@QueryParam`.

What I can think of that the decision might be using the two to differentiate the information pattern. Let me illustrate below my LTPO - less than perfect observation.

PathParam use could be reserved for information category, which would fall nicely into a branch of an information tree. PathParam could be used to drill down to entity class hierarchy.

Whereas, QueryParam could be reserved for specifying attributes to locate the instance of a class.

For example,

- `/Vehicle/Car?registration=123`
- `/House/Colonial?region=newengland`

`/category?instance`

	@GET
	@Path(&quot;/employee/{dept}&quot;)
	Patient getEmployee(@PathParam(&quot;dept&quot;)Long dept, @QueryParam(&quot;id&quot;)Long id) ;

vs `/category/instance`


	@GET
	@Path(&quot;/employee/{dept}/{id}&quot;)
	Patient getEmployee(@PathParam(&quot;dept&quot;)Long dept, @PathParam(&quot;id&quot;)Long id) ;

vs `?category+instance`

	@GET
	@Path(&quot;/employee&quot;)
	Patient getEmployee(@QueryParam(&quot;dept&quot;)Long dept, @QueryParam(&quot;id&quot;)Long id) ;


I don&#39;t think there is a standard convention of doing it. Is there? However, I would like to hear of how people use PathParam vs QueryParam to differentiate their information like I exemplified above. I would also love to hear the reason behind the practice.

When to use @QueryParam vs @PathParam

What response code should be passed to client in case of following scenarios?

1. Invalid data passed while user registration like wrong email format
2. User name/ Email is already exists

I chose 403. I also found following that I feel can be used.

&gt;Wikipedia:

&gt; 412 Precondition Failed : 
&gt;     The server does not meet one of the preconditions that the requester
&gt; put on the request

Suggest code if I should use other than 403.

REST response code for invalid data

I&#39;m writing a REST web app (NetBeans 6.9, JAX-RS, TopLink Essentials) and trying to return JSON **and** HTTP status code. I have code ready and working that returns JSON when the HTTP GET method is called from the client. Essentially:

    @Path(&quot;get/id&quot;)
    @GET
    @Produces(&quot;application/json&quot;)
    public M_機械 getMachineToUpdate(@PathParam(&quot;id&quot;) String id) {
    
        // some code to return JSON ...

        return myJson;
    }

But I *also* want to return an HTTP status code (500, 200, 204, etc.) along with the JSON data.

I tried to use `HttpServletResponse`:

    response.sendError(&quot;error message&quot;, 500);

But this made the browser think it&#39;s a &quot;real&quot; 500 so the output web page was a regular HTTP 500 error page.

I want to return an HTTP status code so that my client-side JavaScript can handle some logic depending on it (to e.g. display the error code and message on an HTML page). Is this possible or should HTTP status codes not be used for such thing?

JAX-RS — How to return JSON and HTTP status code together?

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?

For **java.util.Date** when I do  
  

    @JsonFormat(shape = JsonFormat.Shape.STRING, pattern = &quot;dd/MM/yyyy&quot;)  
      private Date dateOfBirth;

  

then in JSON request when I send   

    { {&quot;dateOfBirth&quot;:&quot;01/01/2000&quot;} }  

it works.

How should I do this for **Java 8&#39;s LocalDate** field??

I tried having   
  

    @JsonDeserialize(using = LocalDateDeserializer.class)  
    @JsonSerialize(using = LocalDateSerializer.class)  
    private LocalDate dateOfBirth;  

It didn&#39;t work.

Can someone please let me know what&#39;s the right way to do this..  

Below are dependencies
 

    &lt;dependency&gt;
        &lt;groupId&gt;org.jboss.resteasy&lt;/groupId&gt;
        &lt;artifactId&gt;jaxrs-api&lt;/artifactId&gt;
         &lt;version&gt;3.0.9.Final&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.4.2&lt;/version&gt;
    &lt;/dependency&gt;
    &lt;dependency&gt;
        &lt;groupId&gt;com.wordnik&lt;/groupId&gt;
        &lt;artifactId&gt;swagger-annotations&lt;/artifactId&gt;
        &lt;version&gt;1.3.10&lt;/version&gt;
    &lt;/dependency&gt;


Java 8 LocalDate Jackson format

I&#39;m wondering whether to use matrix or query parameters in my URLs. I found an older [discussion][1] to that topic not satisfying.

Examples

- URL with query params: http://some.where/thing?paramA=1&amp;paramB=6542
- URL with matrix params: http://some.where/thing;paramA=1;paramB=6542

At first sight matrix params seem to have only advantages:

 - more readable
 - no encoding and decoding of &quot;&amp;&quot; in XML documents is required
 - URLs with &quot;?&quot; are not cached in many cases; URLs with matrix params are cached
 - matrix parameters can appear everywhere in the path and are not limited to its end
 - matrix parameters can have more than one value: `paramA=val1,val2`
 
But there are also disadvantages:

 - only a few frameworks like [JAX-RS][2] support matrix parameters
 - When a browser submits a form via GET, the params become query params. So it ends up in two kinds of parameters for the same task. To not confuse users of the REST services and limit the effort for the developers of the services, it would be easier to use always query params - in this area.

Since the developer of the service can choose a framework with matrix param support, the only remaining disadvantage would be that browsers create by default query parameters.

Are there any other disadvantages? What would you do?


  [1]: https://stackoverflow.com/questions/401981/when-to-use-query-parameters-versus-matrix-parameters
  [2]: https://jsr311.dev.java.net/

URL matrix parameters vs. query parameters

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

I&#39;m trying to POST a `List` of custom objects. 
My JSON in request body is this:

    {
        &quot;collection&quot;: [
            {
                &quot;name&quot;: &quot;Test order1&quot;,
                &quot;detail&quot;: &quot;ahk ks&quot;
            },
            {
                &quot;name&quot;: &quot;Test order2&quot;,
                &quot;detail&quot;: &quot;Fisteku&quot;
            }
        ]
    }

Server side code that handles the request:

    import java.util.Collection;
    
    import javax.ws.rs.Consumes;
    import javax.ws.rs.POST;
    import javax.ws.rs.Path;
    import javax.ws.rs.Produces;
    import javax.ws.rs.core.MediaType;
    import javax.ws.rs.core.Response;
    
    
    @Path(value = &quot;/rest/corder&quot;)
    public class COrderRestService {
    
    	@POST
    	@Produces(MediaType.APPLICATION_JSON)
    	@Consumes(MediaType.APPLICATION_JSON)
    	public Response postOrder(Collection&lt;COrder&gt; orders) {
    		StringBuilder stringBuilder = new StringBuilder();
    		for (COrder c : orders) {
    			stringBuilder.append(c.toString());
    		}
    		System.out.println(stringBuilder);
    		return Response.ok(stringBuilder, MediaType.APPLICATION_JSON).build();
    	}
    }

Entity `COrder`:

    import javax.xml.bind.annotation.XmlRootElement;
    
    @XmlRootElement
    public class COrder {
    	String name;
    	String detail;
    
    	@Override
    	public String toString() {
    		return &quot;COrder [name=&quot; + name + &quot;, detail=&quot; + detail
    				+ &quot;, getClass()=&quot; + getClass() + &quot;, hashCode()=&quot; + hashCode()
    				+ &quot;, toString()=&quot; + super.toString() + &quot;]&quot;;
    	}
    }
    
But an exception is thrown:

    SEVERE: Failed executing POST /rest/corder
    org.jboss.resteasy.spi.ReaderException: org.codehaus.jackson.map.JsonMappingException: Can not deserialize instance of java.util.ArrayList out of START_OBJECT token
     at [Source: org.apache.catalina.connector.CoyoteInputStream@6de8c535; line: 1, column: 1]
    	at org.jboss.resteasy.core.MessageBodyParameterInjector.inject(MessageBodyParameterInjector.java:183)
    	at org.jboss.resteasy.core.MethodInjectorImpl.injectArguments(MethodInjectorImpl.java:88)
    	at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:111)
    	at org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTarget(ResourceMethodInvoker.java:280)
    	at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:234)
    	at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:221)
    	at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:356)
    	at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:179)
    	at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:220)
    	at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56)
    	at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51)
    	at javax.servlet.http.HttpServlet.service(HttpServlet.java:728)
    	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
    	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
    	at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:51)
    	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
    	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
    	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
    	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
    	at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:502)
    	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
    	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:100)
    	at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:953)
    	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
    	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408)
    	at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1041)
    	at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:603)
    	at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312)
    	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
    	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
    	at java.lang.Thread.run(Thread.java:724)

Can not deserialize instance of java.util.ArrayList out of START_OBJECT token

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

I have a question related to REST URL design. I found some relevant posts here [Different RESTful representations of the same resource][1] and here [RESTful url to GET resource by different fields][2] but the responses are not quite clear on what the best practices are and why. Here&#39;s an example.

I have REST URLs for representing &quot;users&quot; resource. I can GET a user with an id or with an email address but the URL representation remains the same for both. Going through a lot of blogs and books I see that people have been doing this in many different ways. For example

read this practice in a book and somewhere on stackoverflow (I can&#39;t seem to find the link again)

    GET /users/id={id}
    GET /users/email={email}

read this practice on a lot of blogs

    GET /users/{id}
    GET /users/email/{email}

Query params are normally used for filtering the results of the resources represented by the URL, but I have seen this practice being used as well

    GET /users?id={id}
    GET /users?email={email}

My question is, out of all these practices, which one would make the most sense to developers consuming the APIs and why? I believe there are no rules set in stone when it comes to REST URL designs and naming conventions, but I just wanted to know which route I should take to help developers better understand the APIs.


  [1]: https://stackoverflow.com/questions/16273390/different-restful-representations-of-the-same-resource
  [2]: https://stackoverflow.com/questions/11104466/restful-url-to-get-resource-by-different-fields

REST API DESIGN - Getting a resource through REST with different parameters but same url pattern

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

After reading a few articles about JAX-RS and JAX-WS, I had a few questions that I want to confirm?

 1. Can JAX-RS do Asynchronous Request like JAX-WS?
 2. Can JAX-RS access a web service that is not running on the Java platform, and vice versa?
 3. What does it mean by &quot;REST is particularly useful for limited-profile devices, such as PDAs and mobile phones&quot;?
 4. What does it mean by &quot;JAX-RS do not require XML messages or WSDL service–API definitions?




What is the difference between JAX-RS and JAX-WS?

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?

Having some sort of proxy between a mobile app and a web-service, we are puzzled by the response when issuing a post request. We receive response with status 200: OK. But we can not find/extract the JSON response body.

    	Client client = ClientBuilder.newClient();
		WebTarget webTarget = client.target(WEBSERVICE_BASE_LOCATION + &quot;mobileDevices?operatorCode=KPNSCP&quot;);
		String jsonString = &quot;{\&quot;osVersion\&quot;:\&quot;4.1\&quot;,\&quot;apiLevel\&quot;:16,\&quot;devicePlatform\&quot;:\&quot;ANDROID\&quot;}&quot;;
		Builder builder = webTarget.request();
		Response response = builder.post(Entity.json(jsonString));

We are using JAX-RS. 
Can someone please provide some hints to extract the JSON body (`String`) from the server response?

Read response body in JAX-RS client from a post request

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 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?

I&#39;m currently looking for ways to create automated tests for a [JAX-RS][1] (Java API for RESTful Web Services) based web service. 

I basically need a way to send it certain inputs and verify that I get the expected responses. I&#39;d prefer to do this via JUnit, but I&#39;m not sure how that can be achieved.

What approach do you use to test your web-services?

**Update:** As entzik pointed out, decoupling the web service from the business logic allows me to unit test the business logic. However, I also want to test for the correct HTTP status codes etc.


  [1]: https://jsr311.dev.java.net/

Testing a JAX-RS Web Service?

Is it possible to set up a JAX-RS application using annotations only? (using Servlet 3.0 and JAX-RS Jersey 1.1.0)

I tried and had no luck. Using some `web.xml` seems required.

----------

**Configuration A (working, but has web.xml configuration)**

web.xml

&lt;!-- language: xml --&gt;

       ...
       &lt;servlet&gt;
          &lt;servlet-name&gt;org.foo.rest.MyApplication&lt;/servlet-name&gt;
       &lt;/servlet&gt;
       &lt;servlet-mapping&gt;
           &lt;servlet-name&gt;org.foo.rest.MyApplication&lt;/servlet-name&gt;
           &lt;url-pattern&gt;/*&lt;/url-pattern&gt;
       &lt;/servlet-mapping&gt;
       ...

Java

    @ApplicationPath(&quot;/&quot;)
    public class MyApplication extends Application {
    	...
    }


----------


**Configuration B (not working, exception thrown)**

    @ApplicationPath(&quot;/&quot;)
    @WebServlet(&quot;/*&quot;) // &lt;-- 
    public class MyApplication extends Application {
    	...
    }

The latter seems to insist that the Application will be a subclass of Servlet (the exception leaves no guesswork)

    java.lang.ClassCastException: org.foo.rest.MyApplication cannot be cast to javax.servlet.Servlet


----------


**Questions**

 1. Why the web.xml definition worked but the annotation didn&#39;t? What&#39;s the difference?

 2. Is there a way to have it worked, e.g. have a JAX-RS Application with no web.xml?

How to set up JAX-RS Application using annotations only (no web.xml)?

I deploy a web-services component to **JBoss Application Server 7** using the **RESTEasy JAX-RS** implementation.

Is there an annotation available to declare required, mandatory **@QueryParam** parameters in **JAX-RS** ? And, if not, what is the &#39;standard&#39; way to deal with situations where such parameters are missing?

My web service (resource) methods return JSON-stringified results when properly invoked with all the mandatory arguments, but I&#39;m not sure what is the best way to indicate to the caller that a required parameter was missing.

Required @QueryParam in JAX-RS (and what to do in their absence)

I have a method;

    @POST
    @Path(&quot;test&quot;)
    @Consumes(MediaType.APPLICATION_JSON)
    public void test(ObjectOne objectOne, ObjectTwo objectTwo)

Now I know I can post a single object in json format, just putting it into the body.
But is it possible to do multiple objects? If so, how?

JAX-RS Post multiple objects

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

I developed a set of restful web services. I couldn&#39;t call any of these methods from remote clients due to the error 
`No &#39;Access-Control-Allow-Origin&#39; header is present on the requested resource.`

The services work perfectly on localhost. Is there any changes or configs to do on the **server side** to resolve the issue. i.e. to enable cross domain requests.

I&#39;m using WildFly 8, JavaEE 7 

How to enable Cross domain requests on JAX-RS web services?

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

JAX-RS has annotations for HTTP verbs such as `GET` (`@GET`) and `POST` (`@POST`) but there is no `@PATCH` annotation. How can I have an annotation for the `PATCH` HTTP verb?
 
Something like the following: 

&lt;!-- language: lang-java --&gt;

    @PATCH
    public Response someCode() {
        // Code to handle the request
    }

How to have a @PATCH annotation for JAX-RS?

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&#39;m trying to inject a *Stateless EJB* into my JAX-RS webservice via annotations. Unfortunately  the EJB is just `null` and I get a `NullPointerException` when I try to use it.


    @Path(&quot;book&quot;)
    public class BookResource {
    
        @EJB
        private BookEJB bookEJB;
    
        public BookResource() {
        }
        
        @GET
        @Produces(&quot;application/xml&quot;)
        @Path(&quot;/{bookId}&quot;)
        public Book getBookById(@PathParam(&quot;bookId&quot;) Integer id)
        {
            return bookEJB.findById(id);
        }
    }

What am I doing wrong?

Here is some information about my machine:

 - Glassfish 3.1 
 - Netbeans 6.9 RC 2
 - Java EE 6

Can you guys show some working example? 

Inject an EJB into JAX-RS (RESTful service)

I&#39;m playing around with JAX-RS, deploying on Tomcat. It&#39;s basically:

    @Path(&quot;/hello&quot;)
    @Produces({&quot;text/plain&quot;})
    public class Hellohandler {

        @GET
        public String hello() {
            return &quot;Hello World&quot;;
        }

    }

Is there any way I can get hold of the `ServletContext` within my JAX-RS resource?


Get ServletContext in JAX-RS resource

I am thinking about buildning a REST API with both websockets and http where I use websockets to tell the client that new data is available or provide the new data to the client directly.

Here are some different ideas of how it could work:  
*ws = websocket*

Idea A:  

 1. David get all users with `GET /users`
 2. Jacob add a user with `POST /users`
 3. A ws message is sent to all clients with info that a new user exist
 4. David recive a message by ws and calls `GET /users`

Idea B:

 1. David get all users with `GET /users`
 2. David register to get ws updates when a change is done to `/users`
 3. Jacob add a user with `POST /users`
 4. The new user is sent to David by ws 

Idea C:

 1. David get all users with `GET /users`
 2. David register to get ws updates when a change is done to `/users`
 3. Jacob add a user with `POST /users` and it gets the id 4
 4. David receive the id 4 of the new user by ws
 5. David get the new user with `GET /users/4`

Idea D:

 1. David get all users with `GET /users`
 2. David register to get ws updates when changes is done to `/users`.
 3. Jacob add a user with `POST /users`
 4. David receive a ws message that changes is done to `/users`
 5. David get only the delta by calling `GET /users?lastcall=&#39;time of step one&#39;`

Which alternative is the best and what are the pros and cons?   
Is it another better &#39;Idea E&#39;?  
Do we even need to use REST or is ws enought for all data?

**Edit**&lt;br /&gt;
To solve problems with data getting out of sync we could provide the header&lt;br /&gt;&quot;If-Unmodified-Since&quot;&lt;br /&gt;https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/If-Unmodified-Since&lt;br /&gt;or &quot;E-Tag&quot;&lt;br /&gt; https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/ETag&lt;br /&gt; or both with PUT requests. 


How to combine websockets and http to create a REST API that keeps data up to date?

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

To my knowledge both serves the same purpose. Except the fact that `@PathVariable` is from Spring MVC and `@PathParam` is from JAX-RS. Any insights on this?

What is the difference between @PathParam and @PathVariable

I&#39;m trying to pass a object via REST web service. Following are my classes explains the functionality that I need using some example codes. 

**Rest Web Service Class method**

    @POST
	@Path(&quot;/find&quot;)
	@Consumes(MediaType.APPLICATION_FORM_URLENCODED)
	@Produces({MediaType.APPLICATION_JSON})
	public Response getDepartments(){
		Response response = new Response();
				
		try {
			
			response.setCode(MessageCode.SUCCESS);
			response.setMessage(&quot;Department Names&quot;);
			Department dept = new Department(&quot;12&quot;, &quot;Financial&quot;);
			response.setPayload(dept);

		} catch (Exception e) {
			response.setCode(MessageCode.ERROR);
			response.setMessage(e.getMessage());
			e.printStackTrace();
		}		
		return response;
	}


**Response Class**

    import java.io.Serializable;
    import javax.xml.bind.annotation.XmlRootElement;
    
    @XmlRootElement
    
    public class Response implements Serializable{
    	
    	private static final long serialVersionUID = 1L;
    
    	public enum MessageCode {
    		SUCCESS, ERROR, UNKNOWN
    	}
    
    	private MessageCode code;
    	private String message;
    	private Object payload;
    	
    	public MessageCode getCode() {
    		return code;
    	}
    	
    	public void setCode(MessageCode code) {
    		this.code = code;
    	}
    	
    	public String getMessage() {
    		return message;
    	}
    	
    	public void setMessage(String message) {
    		this.message = message;
    	}
    	
    	public Object getPayload() {
    		return payload;
    	}
    	
    	public void setPayload(Object payload) {
    		this.payload = payload;
    	}
    }


**Department Class**


    @XmlRootElement
    public class Department implements java.io.Serializable {
    
    	
    	private String deptNo;
    	private String deptName;
    
    
    	public Department() {
    	}
    
    	public Department(String deptNo, String deptName) {
    		this.deptNo = deptNo;
    		this.deptName = deptName;
    	}
    
    	public String getDeptNo() {
    		return this.deptNo;
    	}
    
    	public void setDeptNo(String deptNo) {
    		this.deptNo = deptNo;
    	}
    
    	public String getDeptName() {
    		return this.deptName;
    	}
    
    	public void setDeptName(String deptName) {
    		this.deptName = deptName;
    	}
    
    }

When I make a call to getDepartments method in the rest web service class it returns following exceptions. But If I change the type **Object** of the **payload** to **Department** in the Response class it returns the json response correctly. But since I need to use this Response class for different types of Classes I can&#39;t restring the payload to one class type. Can anyone please help me in this matter?

**Stack Trace** 


    Dec 27, 2012 9:34:18 PM com.sun.jersey.spi.container.ContainerResponse logException
    SEVERE: Mapped exception to response: 500 (Internal Server Error)
    javax.ws.rs.WebApplicationException: javax.xml.bind.MarshalException
     - with linked exception:
    [javax.xml.bind.JAXBException: class Department nor any of its super class is known to this context.]
    	at com.sun.jersey.core.provider.jaxb.AbstractRootElementProvider.writeTo(AbstractRootElementProvider.java:159)
    	at com.sun.jersey.spi.container.ContainerResponse.write(ContainerResponse.java:306)
    	at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1437)
    	at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1349)
    	at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1339)
    	at com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:416)
    	at com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:537)
    	at com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:699)
    	at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    	at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
    	at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:401)
    	at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
    	at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
    	at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
    	at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450)
    	at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
    	at org.mortbay.jetty.Server.handle(Server.java:326)
    	at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
    	at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:945)
    	at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:756)
    	at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218)
    	at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
    	at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410)
    	at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
    Caused by: javax.xml.bind.MarshalException
     - with linked exception:
    [javax.xml.bind.JAXBException: class Department nor any of its super class is known to this context.]
    	at com.sun.xml.bind.v2.runtime.MarshallerImpl.write(MarshallerImpl.java:323)
    	at com.sun.xml.bind.v2.runtime.MarshallerImpl.marshal(MarshallerImpl.java:177)
    	at com.sun.jersey.json.impl.BaseJSONMarshaller.marshallToJSON(BaseJSONMarshaller.java:103)
    	at com.sun.jersey.json.impl.provider.entity.JSONRootElementProvider.writeTo(JSONRootElementProvider.java:136)
    	at com.sun.jersey.core.provider.jaxb.AbstractRootElementProvider.writeTo(AbstractRootElementProvider.java:157)
    	... 23 more
    Caused by: javax.xml.bind.JAXBException: class Department nor any of its super class is known to this context.
    	at com.sun.xml.bind.v2.runtime.XMLSerializer.reportError(XMLSerializer.java:250)
    	at com.sun.xml.bind.v2.runtime.XMLSerializer.reportError(XMLSerializer.java:265)
    	at com.sun.xml.bind.v2.runtime.XMLSerializer.childAsXsiType(XMLSerializer.java:657)
    	at com.sun.xml.bind.v2.runtime.property.SingleElementNodeProperty.serializeBody(SingleElementNodeProperty.java:156)
    	at com.sun.xml.bind.v2.runtime.ClassBeanInfoImpl.serializeBody(ClassBeanInfoImpl.java:344)
    	at com.sun.xml.bind.v2.runtime.XMLSerializer.childAsSoleContent(XMLSerializer.java:597)
    	at com.sun.xml.bind.v2.runtime.ClassBeanInfoImpl.serializeRoot(ClassBeanInfoImpl.java:328)
    	at com.sun.xml.bind.v2.runtime.XMLSerializer.childAsRoot(XMLSerializer.java:498)
    	at com.sun.xml.bind.v2.runtime.MarshallerImpl.write(MarshallerImpl.java:320)
    	... 27 more
    Caused by: javax.xml.bind.JAXBException: class Department nor any of its super class is known to this context.
    	at com.sun.xml.bind.v2.runtime.JAXBContextImpl.getBeanInfo(JAXBContextImpl.java:611)
    	at com.sun.xml.bind.v2.runtime.XMLSerializer.childAsXsiType(XMLSerializer.java:652)
    	... 33 more




javax.xml.bind.JAXBException: Class *** nor any of its super class is known to this context

I am getting the following error response from the server.

&gt; HTTP Status 500 -
&gt; 
&gt; type Exception report
&gt; 
&gt; message
&gt; 
&gt; descriptionThe server encountered an internal error () that prevented
&gt; it from fulfilling this request.
&gt; 
&gt; exception
&gt; 
&gt; javax.servlet.ServletException:
&gt; java.lang.UnsupportedOperationException: Attempted to serialize
&gt; java.lang.Class: org.hibernate.proxy.HibernateProxy. Forgot to
&gt; register a type adapter?
&gt; 
&gt; root cause
&gt; 
&gt; java.lang.UnsupportedOperationException: Attempted to serialize
&gt; java.lang.Class: org.hibernate.proxy.HibernateProxy. Forgot to
&gt; register a type adapter?

From Java debugger:

    org.hibernate.proxy.pojo.javassist.JavassistLazyInitializer@7632012e

I am using Gson to convert my Java objects to JSON. Below I have pasted some of my code.

This is my resource:

    @Stateless
    @LocalBean
    @Path(&quot;/autos&quot;)
    @Produces(MediaType.APPLICATION_JSON)
    public class AutoResource {
    
        @EJB
        private CarAssembler warehouse;
        @Context
        private UriInfo uriInfo;
    
        @GET
        public Response allAutos() {
            // Building a context, lots of code...
            // Creating a Gson instance and configures it...

            final Auto auto = warehouse.list(context);
            final String autoJson = gson.toJson(auto);
    
            return Response.ok(autoJson).build();
        }
    }

The CarAssembler is just an service which invokes a repository. I have not pasted the code of the service here.

Repository:

    @Override
    public Question findById(final int id, final FetchType fetchType) {

        final Auto question = getEntityManager().find(Auto.class, id);

        if (fetchType == FetchType.LAZY) {
            return auto;
        }

        Hibernate.initialize(auto.getManufacturer());
        Hibernate.initialize(auto.getAssemblyHouse());

        return auto;
    }

As you see, I provide both lazy and eager loading of objects. I use Hibernate.initialize to eager fetch JPA associations. However, the question is how I can fix the proxy error I am getting. Why come there is only AssemblyHouse that is still attached to JavaAssist, while Manufacturer is not (I have seen the type in Java Debugger). How do I know when to unproxy objects? Should I unproxy all associations this auto may have? And in which layer of my code? Does it affect the performance of my application when I unproxy? Are there other solutions? I see from the error message that I can make a type adapter. Yes, I could but then I have to do that for all domain objects to be sure that conversion is done correctly. Maybe other objects in my domain starts failing when I try to convert it into JSON representation too, but I don&#39;t know when or why. Is it just luck that the other objects are fine? 

This is the way I am unproxing objects, but I have not implemented it yet, because I don&#39;t know if this is good or bad, and in what layer to do this, and when I should do it. Should I unproxy objects all the time?

    public class HibernateUtilities {
    
        public static &lt;T&gt; T unproxy(T proxy) {
            if (proxy == null) {
                return null;
            }
    
            if (proxy instanceof HibernateProxy) {
                Hibernate.initialize(proxy);
    
                HibernateProxy hibernateProxy = (HibernateProxy) proxy;
                T unproxiedObject = (T) hibernateProxy.getHibernateLazyInitializer().getImplementation();
    
                return unproxiedObject;
            }
    
            return proxy;
        }
    }


----------
Stacktrace as requested:

&lt;pre&gt;
[#|2012-11-22T17:17:13.285+0100|WARNING|glassfish3.1.2|javax.enterprise.system.container.web.com.sun.enterprise.web|_ThreadID=71;_ThreadName=Thread-8;|StandardWrapperValve[javax.ws.rs.core.Application]:
PWC1406: Servlet.service() for servlet javax.ws.rs.core.Application
threw exception java.lang.UnsupportedOperationException: Attempted to
serialize java.lang.Class: org.hibernate.proxy.HibernateProxy. Forgot
to register a type adapter?
    at com.google.gson.internal.bind.TypeAdapters$1.write(TypeAdapters.java:64)
    at com.google.gson.internal.bind.TypeAdapters$1.write(TypeAdapters.java:61)
    at com.google.gson.internal.bind.TypeAdapterRuntimeTypeWrapper.write(TypeAdapterRuntimeTypeWrapper.java:68)
    at com.google.gson.internal.bind.ArrayTypeAdapter.write(ArrayTypeAdapter.java:93)
    at com.google.gson.internal.bind.TypeAdapterRuntimeTypeWrapper.write(TypeAdapterRuntimeTypeWrapper.java:68)
    at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$1.write(ReflectiveTypeAdapterFactory.java:89)
    at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$Adapter.write(ReflectiveTypeAdapterFactory.java:195)
    at com.google.gson.internal.bind.TypeAdapterRuntimeTypeWrapper.write(TypeAdapterRuntimeTypeWrapper.java:68)
    at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$1.write(ReflectiveTypeAdapterFactory.java:89)
    at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$Adapter.write(ReflectiveTypeAdapterFactory.java:195)
    at com.google.gson.internal.bind.TypeAdapterRuntimeTypeWrapper.write(TypeAdapterRuntimeTypeWrapper.java:68)
    at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$1.write(ReflectiveTypeAdapterFactory.java:89)
    at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$Adapter.write(ReflectiveTypeAdapterFactory.java:195)
    at com.google.gson.internal.bind.TypeAdapterRuntimeTypeWrapper.write(TypeAdapterRuntimeTypeWrapper.java:68)
    at com.google.gson.internal.bind.CollectionTypeAdapterFactory$Adapter.write(CollectionTypeAdapterFactory.java:96)
    at com.google.gson.internal.bind.CollectionTypeAdapterFactory$Adapter.write(CollectionTypeAdapterFactory.java:60)
    at com.google.gson.internal.bind.TypeAdapterRuntimeTypeWrapper.write(TypeAdapterRuntimeTypeWrapper.java:68)
    at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$1.write(ReflectiveTypeAdapterFactory.java:89)
    at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$Adapter.write(ReflectiveTypeAdapterFactory.java:195)
    at com.google.gson.Gson.toJson(Gson.java:586)
    at com.google.gson.Gson.toJson(Gson.java:565)
    at com.google.gson.Gson.toJson(Gson.java:520)
    at com.myapp.AutoResource.produceAuto(AutoResource.java:48)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:601)
    at org.glassfish.ejb.security.application.EJBSecurityManager.runMethod(EJBSecurityManager.java:1052)
    at org.glassfish.ejb.security.application.EJBSecurityManager.invoke(EJBSecurityManager.java:1124)
    at com.sun.ejb.containers.BaseContainer.invokeBeanMethod(BaseContainer.java:5388)
    at com.sun.ejb.EjbInvocation.invokeBeanMethod(EjbInvocation.java:619)
    at com.sun.ejb.containers.interceptors.AroundInvokeChainImpl.invokeNext(InterceptorManager.java:800)
    at com.sun.ejb.EjbInvocation.proceed(EjbInvocation.java:571)
    at com.sun.ejb.containers.interceptors.SystemInterceptorProxy.doAround(SystemInterceptorProxy.java:162)
    at com.sun.ejb.containers.interceptors.SystemInterceptorProxy.aroundInvoke(SystemInterceptorProxy.java:144)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:601)
    at com.sun.ejb.containers.interceptors.AroundInvokeInterceptor.intercept(InterceptorManager.java:861)
    at com.sun.ejb.containers.interceptors.AroundInvokeChainImpl.invokeNext(InterceptorManager.java:800)
    at com.sun.ejb.containers.interceptors.InterceptorManager.intercept(InterceptorManager.java:370)
    at com.sun.ejb.containers.BaseContainer.__intercept(BaseContainer.java:5360)
    at com.sun.ejb.containers.BaseContainer.intercept(BaseContainer.java:5348)
    at com.sun.ejb.containers.EJBLocalObjectInvocationHandler.invoke(EJBLocalObjectInvocationHandler.java:214)
    at com.sun.ejb.containers.EJBLocalObjectInvocationHandlerDelegate.invoke(EJBLocalObjectInvocationHandlerDelegate.java:89)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:601)
    at com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
    at com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
    at com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
    at com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:288)
    at com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
    at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
    at com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
    at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1469)
    at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1400)
    at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1349)
    at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1339)
    at com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:416)
    at com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:537)
    at com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:708)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:770)
    at org.apache.catalina.core.StandardWrapper.service(StandardWrapper.java:1550)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:281)
    at org.apache.catalina.core.StandardContextValve.__invoke(StandardContextValve.java:175)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:655)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:595)
    at org.apache.catalina.core.StandardHostValve.__invoke(StandardHostValve.java:161)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java)
    at org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:331)
    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:231)
    at com.sun.enterprise.v3.services.impl.ContainerMapper$AdapterCallable.call(ContainerMapper.java:317)
    at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:195)
    at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:860)
    at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:757)
    at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1056)
    at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:229)
    at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:137)
    at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:104)
    at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:90)
    at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:79)
    at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:54)
    at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:59)
    at com.sun.grizzly.ContextTask.run(ContextTask.java:71)
    at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:532)
    at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:513)
    at java.lang.Thread.run(Thread.java:722) |#]
&lt;/pre&gt;

Could not serialize object cause of HibernateProxy

I have a service defined as follows.

`public String getData(@QueryParam(&quot;date&quot;) Date date)`

I&#39;m trying to pass a `java.util.Date` to it from my client (which is jaxrs:client of CXF, not a generic HTTP client or browser).

My service receives the date as `Thu Mar 01 22:33:10 IST 2012` in the HTTP URL. Since CXF won&#39;t be able to create a `Date` object using this String, my client receives a 404 error.
I tried using a `ParameterHandler` on the service side, but I still can&#39;t parse it successfully because I&#39;m not expecting the date in any specific format.

As per [this post][1], passing a `Date` is supposed to work out of the box, but I can&#39;t seem to get the basic case working. Am I required to do anything in order to successfully pass a Date object from my client to service? Appreciate any help.

Thanks


  [1]: https://stackoverflow.com/questions/583973/jax-rs-jersey-how-to-customize-error-handling &quot;this post&quot;

CXF JAXRS - How do I pass Date as QueryParam

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 am new to using JAX-RS and wrote a sample application that outputs a json object. but I am getting an exception. Here is my code:


    @Path(&quot;/hello&quot;)
    public class HelloWorldService {
     
    	@GET
    	@Path(&quot;/query/{artist_id}&quot;)
    	@Produces(&quot;application/json&quot;)
    	public Data getMsg(@PathParam(&quot;artist_id&quot;) int artist_id,
    							@QueryParam(&quot;from&quot;) int from,
    							@QueryParam(&quot;to&quot;) int to) {
    		Data d=new Data();
    		d.setName(&quot;Mateen&quot;);
    		d.setRoll(77);
    		return d;
 
    	}
   }

My data is simply a POJO class:

    @XmlRootElement
    public class Data {
    	private int roll;
    	private String name;
    	public int getRoll() {
    		return roll;
    	}
    	public void setRoll(int roll) {
    		this.roll = roll;
    	}
    	public String getName() {
    		return name;
    	}
    	public void setName(String name) {
    		this.name = name;
    	}
    }

I get an exception:

    javax.ws.rs.WebApplicationException: 
        com.sun.jersey.api.MessageException: 
        A message body writer for Java class com.abc.data.Data, 
        and Java type class com.abc.data.Data, 
        and MIME media type application/json was not found


What am i doing wrong ?

A message body writer for Java class not found

How can I set the charset with JAX-RS? I&#39;ve tried `@Produces(&quot;text/html; charset=UTF-8&quot;)` but that was ignored and only `text/html` was send with the HTTP header. I want to set the charset within a MessageBodyWriter, but don&#39;t want to extract the media type by analysing the @Produces annotation via reflection by myself.

How to set the charset with JAX-RS?

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 wrote code that generate Excel file using REST JAX-RS and I confirmed that the generated Excel file is in GlassFish server directory.

But my goal is when user click on the button (which generate Excel .xls), I want download popup to show up asking user whether to save or open the .xls file just like any other web services doing for downloading any type of files.

According to my search, the step is:

1. generate Excel .xls (DONE)

2. write the excel to stream 

3. in JAX-RS file, set response header to something like,

    String fileName = &quot;Blah_Report.xls&quot;;
    response.setHeader(&quot;Content-Disposition&quot;, &quot;attachment; filename=&quot; + fileName);

My question is I&#39;m doing all of this in JAX-RS file and I don&#39;t have HttpServletResponse object available.

According to the answer from 
https://stackoverflow.com/questions/1493415/add-response-header-to-jax-rs-webservice

He says:

&gt; You can inject a reference to the
&gt; actual HttpServletResponse via the
&gt; @Context annotation in your webservice
&gt; and use addHeader() etc. to add your
&gt; header.

I can&#39;t really figure what exactly that means without sample code..








How to set response header in JAX-RS so that user sees download popup for Excel?

Today I read about Restful services. Basically what I understand that is Restful webservices will work on HTTP request methods rather than normal webservice will work on SOAP request.

What is the need for Restful services as normal servlet can also work on the HTTP methods?

Servlet vs RESTful

I&#39;ve been doing some work with the JAX-RS reference implementation (Jersey).
I know of at least two other frameworks (Restlet &amp; Apache CXF).

My question is: Has anyone done some comparison between those frameworks and if so, which framework would you recommend and why?

JAX-RS Frameworks

Is it possible to do something like that?

    import javax.ws.rs.GET;
    import javax.ws.rs.Path;
    
    public class xxx
    {
      @GET
      @Path(value = &quot;path1&quot;)
      public Response m1()
      {
        ...
      }
    
      @GET
      @Path(value = &quot;path2&quot;)
      public Response m1()
      {
        ...
      }
    }

I&#39;m using RESTEasy btw.


JAX-RS: Multiple paths

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 Jax Rs Solutions on Gang of Coders

Total of 49 Jax Rs Solutions