[ACCEPTED]-How to get jersey logs at server?-jersey

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

This filter will log request/response headers and entities.

Here's 3 what you need to add to your ResourceConfig class:

@ApplicationPath("/")
public class MyApplication extends ResourceConfig {

    public MyApplication() {
        // Resources.
        packages(MyResource.class.getPackage().getName());

        register(LoggingFilter.class);    
    }
}

Note 2 that the same filter also works on the client 1 side.

Client client = Client.create();
client.addFilter(new LoggingFilter());

Jersey 2 has deprecated LoggingFilter and you now need 3 to use LoggingFeature. In order to use it with a client 2 you can use the following snipette:

this.client = ClientBuilder
            .newBuilder()
            .property(LoggingFeature.LOGGING_FEATURE_VERBOSITY_CLIENT, LoggingFeature.Verbosity.PAYLOAD_ANY)
            .property(LoggingFeature.LOGGING_FEATURE_LOGGER_LEVEL_CLIENT, "WARNING")
            .build();

and 1 on the server side:

ResourceConfig config = new ResourceConfig(HelloWorldResource.class);
config.register(LoggingFeature.class);

Jersey 2.0 uses org.glassfish.jersey.filter.LoggingFilter
You can connect it with 3 help of web.xml

<!-- Register my custom provider (not needed if it's in my.package) AND LoggingFilter. -->
        <init-param>
            <param-name>jersey.config.server.provider.classnames</param-name>
            <param-value>org.glassfish.jersey.filter.LoggingFilter</param-value>
        </init-param>

More explanations can be found 2 here

upd:

After version 2.23 LoggingFilter is deprecated and LoggingFeature should 1 be used. More info can be found in official documentation

For Jersey 1.2 add the following entry into 1 web.xml inside the servlet tag:

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

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

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

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

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

Get the XML from the response

Using a REST client like 2 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);

// log 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 1 test should fail (if I'm right).