jersey-2.0

When I send this request: {"invalidField": "value", "date": "value"} to my rest service: @PUT @Consumes("application/json") public void putJson(Test content) { System.out.println(content.toString()); } I expected to get an exception because: There is no invalidField in my domain model. Date format is not valid. But really I get test object with null values. My dmain model is: public class Test { private String name; private Date date; //getters and setters here } I think this is not a valid behavior. How can I fix that? Thanks for help. Solution: As Blaise Doughan said, it is required to

I have a Resource Class , with a @ManagedAsync method Class which looks like this: @Path("my-resource") public class MyResource extends BaseResource{ private DatumDAO datumDAO; public MyResource(DatumDAO datumDAO){ this.datumDAO = datumDAO; } public void cleanDatum(Datum datum){ //time taking operations } @GET @ManagedAsync @Path("/cleanup/{from}/{till}/") @Consumes(MediaType.APPLICATION_JSON) @Produces(MediaType.APPLICATION_JSON) @UnitOfWork public void cleanupDirtyData(@Suspended final AsyncResponse asyncResponse, @PathParam("from") DateTimeParam from, @PathParam("till") DateTimeParam till)

We're in the process to upgrade our Web application (running on Tomcat7) from Jersey 1.7 to Jersey 2.4.1. I managed to have the server-side working now, but the JUnit tests which are using jersey-client are throwing the AbstractMethodError: java.lang.AbstractMethodError: javax.ws.rs.core.UriBuilder.uri(Ljava/lang/String;)Ljavax/ws/rs/core/UriBuilder; at javax.ws.rs.core.UriBuilder.fromUri(UriBuilder.java:119) at org.glassfish.jersey.client.JerseyWebTarget.<init>(JerseyWebTarget.java:72) at org.glassfish.jersey.client.JerseyClient.target(JerseyClient.java:180) at org.glassfish.jersey.client

I am using Jersey 2 to implement JAR-RS 2.0 in an IBM WebSphere 8.5 environment. After reading this post JAX-RS Jersey 2.10 support in Websphere 8 I managed to get this working. However, is it possible to bundle the JAX-RS Jars within the WAR and deploy the application without the need to create an isolated shared library? If this is not possible, can someone please explain why this is the case? I understand the deployment time advantage of having the Jars in a library, but I would prefer to build the entire application including dependencies into a single WAR. -- EDIT -- It appears that you

Continuation of topic Jersey 2 + HK2 - @ApplicationScoped not working . I already know, how to bind classes in order to @Inject them properly. Do you have any ideas, how to automize this process? Putting every single service in bind statements seems like very bad smell in my application. After using Google's Guice for a number of years, I am accustomed to the availability of a Just-In-Time binder, allowing the injection of arbitrary types without requiring any upfront configuration. I too found the idea of having to explicitly bind every service to be a bad code smell. I'm also not crazy about

First time implementing JAX-RS Client API in an application and I am having some small problems when it comes to storing the response data, which is returned as JSON as a Java BEAN. Refer to the following code snippets below which demonstrate how I have implemented it thus far. object = client.target(uri).request().post(Entity.entity(requestObject, APPLICATION_JSON), Object.class); Essentially, I would like to store the returned JSON response from the web service into my Java BEAN, which in this scenario is named object . requestObject is obviously the data which I am sending through to the

I am in the progress to migrate a Jerset 1.x client project to Jersey 2.0. I found that GZIPContentEncodingFilter does not exist any longer. Is there something similar? I stumbled over GZIPEncoder but am not sure how to plug it in. In Jersey 1.17 I use: WebResource r = ... r.register(new GZIPContentEncodingFilter()); In Jersey 2.0 I search for somethink like: WebTarget r = ... r.register(new GZIPContentEncodingFilter()); Use WebTarget r = ... r.register(GZIPEncoder.class); Most of details can be obtained from Jersey's own unit tests. So to allow responses to be compressed using GZip or Deflate