ansaurus

Question

Answer 1

A:

Could you show us your client code and tell us about the request as well?

This exception seems to point at the JAXB unmarshalling step. Apparently you received some XML from your REST API, but you don't get what you're waiting for.

Maybe the XSD you're using for marshalling/unmarshalling is outdated or just plain wrong.
Maybe you're trying to get the wrong entity from the response.

Try these steps and give us some more details about your problem:

Get the XML from the response

Using a REST client like Client REST simple (a chrome extension), or your code:

Builder builder = webResource.path("/yourapi/").accept("application/xml");

// get the client response
ClientResponse response = builder.get(ClientResponse.class);

// check the HTTP Status
logger.log("HTTP Status: "response.getStatus());

// bypass the jaxb step and get the full response
// MyResource myResource = response.getEntity(MyResource.class);
String myResource = response.getEntity(String.class);
logger.log(myResource);

Validate this XML with the XSD you're using

This test should fail (if I'm right).

Brian Clozel 2010-02-26 12:45:21

thanks Brian. This particular issue was due to invalid construction of URI. I made something like [look at mutation] http://localhost/blah/http://localhost/blah. It was hitting the server and server returned an error code and client failed due to library not handling null.com.sun.xml.internal.ws.message.AbstractMessageImpl:107 return (T) unmarshaller.unmarshal(readPayloadAsSource());readPayloadAsSource() was returning null. So the exception message was more of red herring.I was mainly interested in knowing how to get jersey logs at server - so that I will know what server is returning.

Fakrudeen 2010-02-26 16:17:10

Hey Fakrudeen. You really should edit your question to make that clear. I added another answer (I hope this one answsers your question).

Brian Clozel 2010-03-02 09:35:24

Thanks! that was what I was looking for. BTW, I thought my very first line says ["How do I enable jersey logs at server side?"] what I want .

Fakrudeen 2010-03-02 11:28:33

Agree. But then you elaborate about a JAXB problem on the client side - that's why I thought I was on the right path when I submitted my first answer.Don't get me wrong though, I think both questions and answers are relevant (and can be useful to jersey users) - rewriting part of it could help others.

Brian Clozel 2010-03-02 12:28:53

Answer 2

+2 A:

If you want to turn on logging on the server side, you need to register the LoggingFilter Jersey filter (on the container side).

This filter will log request/response headers and entities.

Here's what you need to add to your web.xml (copied/pasted from the Javadoc):

<init-param>
  <param-name>com.sun.jersey.spi.container.ContainerRequestFilters</param-name>
  <param-value>com.sun.jersey.api.container.filter.LoggingFilter</param-value>
</init-param>
<init-param>
  <param-name>com.sun.jersey.spi.container.ContainerResponseFilters</param-name>
  <param-value>com.sun.jersey.api.container.filter.LoggingFilter</param-value>
</init-param>

There's also a LoggingFilter designed for the client side.

Brian Clozel 2010-03-02 09:34:54

ansaurus

tags:

views:

answers:

How to get jersey logs at server?

Get the XML from the response

Validate this XML with the XSD you're using

related questions