If you get this exception with no other clues anywhere (even if it says you should get more clues "in the logs"):

09-May-2011 15:37:38 org.apache.catalina.core.StandardContext
filterStart SEVERE: Exception starting filter Jersey Filter
com.sun.jersey.api.container.ContainerException: Fatal issues found at
class See logs for more details.
at com.sun.jersey.server.impl.application.WebApplicationImpl.newResourceClass(
at com.sun.jersey.server.impl.application.WebApplicationImpl.getResourceClass(
at com.sun.jersey.server.impl.application.WebApplicationImpl.processRootResources(
at com.sun.jersey.server.impl.application.WebApplicationImpl.initiate(
at com.sun.jersey.server.impl.application.WebApplicationImpl.initiate(
at com.sun.jersey.spi.container.servlet.ServletContainer.initiate(
at com.sun.jersey.spi.container.servlet.ServletContainer$InternalWebComponent.initiate(
at com.sun.jersey.spi.container.servlet.WebComponent.load(
at com.sun.jersey.spi.container.servlet.WebComponent.init(
at com.sun.jersey.spi.container.servlet.ServletContainer.init(
at com.sun.jersey.spi.container.servlet.ServletContainer.init(

It might very well be that you have an annotated web service method that lacks annotation on (one of) its parameters. In mycase, I had annotations on the first parameter, but not the second:

public Response getSomeResponse(@QueryParam("first") String pFirst,
String pSecond) {
Missing @QueryParam

And yes, I checked all the logs; the application server log, the system out log and the LOG4J log, and no, there were no more exception details ;-)

Licensed under CC BY Creative Commons License ~ ✉ torstein.k.johansen @ gmail ~ 🐘 ~ 🐦 @torsteinkrause