If you are using Jersey then url to wadl would be something like http://localhost:8080/applicationname/application.wadl You may need to add the resource base into the url e.g. http://localhost:8080/applicationname/resources/application.wadl
You need to annotate your exception mapper with @Provider, otherwise it will never get registered with the JAX-RS runtime. @Provider public class UserNotFoundMapper implements ExceptionMapper<UserNotFoundException> { @Override public Response toResponse(UserNotFoundException ex) { return Response.status(404).entity(ex.getMessage()).type(“text/plain”) .build(); } }
I’ll first get to the question “JSR311 it is a specification request. Which means it is supposed to be a document. Why then is it a jar?” Except the last (jersey-core), all those jars are “specification” jars. The JAX-RS (as well as many other Java) specifications define contracts (or interfaces) that implementators should implement the … Read more
You can use following code String responseAsString = response.readEntity(String.class);
Actually, according to the specification, adding @Valid is exactly for this usecase. From the JSR 303 specification: In addition to supporting instance validation, validation of graphs of object is also supported. The result of a graph validation is returned as a unified set of constraint violations. Consider the situation where bean X contains a field … Read more
It’s probably not so much a bug as a limitation of the Servlet spec. The details of how a JAX-RS @ApplicationPath is handled is implementation specific, and I can’t speak for all implementations, but I’d guess the typical approach is to simply use it as a servlet URL pattern. Taking a look at Jersey’s ServletContainerInitializer … Read more
This is how you enable slashes in path params: @Path(“{inchiname : .+}”) public String get3DCoordinates(@PathParam(“inchiname”)String inchiName)
JAX-WS is an API for SOAP-based WS, and using it for RESTful WebServices is not the best way to go about things. So if you’re looking to implement a RESTful WebService, use JAX-RS .
I managed to do it in Resteasy “the JAX-RS way”, so it should work on every compliant implementation like Jersey (recently successfully tested on JEE7 server Wildfly 8, it just required a few changes to the Jackson part because they changed a few APIs). You must define a ContextResolver (check that Produces contains the correct … Read more
The @Context annotation allows you to inject request/response context details into JAX-RS provider and resource classes. Injection can be performed into a class field, a bean property or a method parameter. The following list summarizes all the types that can be injected using the @Context annotation, according to the JAX-RS 2.0 specification: javax.ws.rs.core.Application javax.ws.rs.core.HttpHeaders javax.ws.rs.core.Request … Read more