I got answer here. One will just have to define a custom Patch annotation, what that means is that you will have to write a PATCH.java file with following code: @Target({ElementType.METHOD}) @Retention(RetentionPolicy.RUNTIME) @HttpMethod(“PATCH”) public @interface PATCH { } Import the package containing PATCH.java and then you can use it like other HTTP method annotations: @PATCH … Read more
You can’t have two Content-Types (well technically that’s what we’re doing below, but they are separated with each part of the multipart, but the main type is multipart). That’s basically what you are expecting with your method. You are expecting mutlipart and json together as the main media type. The Employee data needs to be … Read more
I was wondering the same thing, so after a bit of research I found that the easiest way was simply to use a JAX-RS ContainerResponseFilter to add the relevant CORS headers. This way you don’t need to replace the whole web services stack with CXF (Wildfly uses CXF is some form, but it doesn’t look … Read more
You can not use your method like this as correctly stated by Tarlog. However, you can do this: @POST @Path(“test”) @Consumes(MediaType.APPLICATION_JSON) public void test(List<ObjectOne> objects) or this: @POST @Path(“test”) @Consumes(MediaType.APPLICATION_JSON) public void test(BeanWithObjectOneAndObjectTwo containerObject) Furthermore, you can always combine your method with GET parameters: @POST @Path(“test”) @Consumes(MediaType.APPLICATION_JSON) public void test(List<ObjectOne> objects, @QueryParam(“objectTwoId”) long objectTwoId)
I was able to fix it by install jersey-media-json-jackson Add the dependency to pom.xml <dependency> <groupId>org.glassfish.jersey.media</groupId> <artifactId>jersey-media-json-jackson</artifactId> <scope>runtime</scope> </dependency>
Note: Make sure to read the UPDATE at the bottom. The original answer includes a “lazy” implementation of the CORS filter With Jersey, to handle CORS, you can just use a ContainerResponseFilter. The ContainerResponseFilter for Jersey 1.x and 2.x are a bit different. Since you haven’t mentioned which version you’re using, I’ll post both. Make … Read more
** PLEASE READ IF YOU USE TOMCAT OR JETTY! ** The accepted answer does work, but only if the webapp is deployed to an app server like Glassfish or Wildfly, and possibly servlet containers with EE extensions like TomEE. It doesn’t work on standard servlet containers like Tomcat, which I’m sure most people looking for … Read more
Good question. Unfortunately (or maybe fortunately) there is no mechanism in JAX-RS to make any params mandatory. If a parameter is not supplied it’s value will be NULL and your resource should deal with it accordingly. I would recommend to use WebApplicationException to inform your users: @GET @Path(“/some-path”) public String read(@QueryParam(“name”) String name) { if … Read more
Jersey comes with a great RESTful client API that makes writing unit tests really easy. See the unit tests in the examples that ship with Jersey. We use this approach to test the REST support in Apache Camel, if you are interested the test cases are here
Why use JAX-RS / Jersey? Short Answer Because it makes the development of RESTful services easier. Long Answer JAX-RS is a standard that makes it easy to create a RESTful service that can be deployed to any Java application server: GlassFish, WebLogic, WebSphere, JBoss, etc. JAX-RS is part of Java EE, and when JAX-RS is … Read more