Standard JAX-RS uses an Application as its configuration class. ResourceConfig extends Application. There are three main ways (in a servlet container) to configure Jersey (JAX-RS): With only web.xml With both web.xml and an Application/ResourceConfig class With only an Application/ResourceConfig class annotated with @ApplicationPath. With only web.xml It is possible to configure the application in a … Read more
Try this: String output = response.getEntity(String.class); EDIT Thanks to @Martin Spamer to mention that it will work for Jersey 1.x jars only. For Jersey 2.x use String output = response.readEntity(String.class);
You can access a single param via @QueryParam(“name”) or all of the params via the context: @POST public Response postSomething(@QueryParam(“name”) String name, @Context UriInfo uriInfo, String content) { MultivaluedMap<String, String> queryParams = uriInfo.getQueryParameters(); String nameParam = queryParams.getFirst(“name”); } The key is the @Context jax-rs annotation, which can be used to access: UriInfo, Request, HttpHeaders, SecurityContext, … Read more
Another important point JAX-WS represents SOAP JAX-RS represents REST How to choose between JAX-RS and JAX-WS web services implementation?
JAX-RS is an specification (just a definition) and Jersey is a JAX-RS implementation.
Query parameters are added to the URL after the ? mark, while a path parameter is part of the regular URL. In the URL below tom could be the value of a path parameter and there is one query parameter with the name id and value 1: http://mydomain.example/tom?id=1
I managed to get a ZIP file or a PDF file by extending the StreamingOutput object. Here is some sample code: @Path(“PDF-file.pdf/”) @GET @Produces({“application/pdf”}) public StreamingOutput getPDF() throws Exception { return new StreamingOutput() { public void write(OutputStream output) throws IOException, WebApplicationException { try { PDFGenerator generator = new PDFGenerator(getEntity()); generator.generatePDF(output); } catch (Exception e) { … Read more
Your @POST method should be accepting a JSON object instead of a string. Jersey uses JAXB to support marshaling and unmarshaling JSON objects (see the jersey docs for details). Create a class like: @XmlRootElement public class MyJaxBean { @XmlElement public String param1; @XmlElement public String param2; } Then your @POST method would look like the … Read more
In my experience, GET /users/{id} GET /users/email/{email} is the most common approach. I would also expect the methods to return a 404 Not Found if a user doesn’t exist with the provided id or email. I wouldn’t be surprised to see GET /users/id/{id}, either (though in my opinion, it is redundant). Comments on the other … Read more
Providers are a simply a way of extending and customizing the JAX-RS runtime. You can think of them as plugins that (potentially) alter the behavior of the runtime, in order to accomplish a set of (program defined) goals. Providers are not the same as resources classes, they exist, conceptually, at a level in-between resources classes … Read more