If you get this exception with no other clues anywhere (even if it says you should get more clues "in the logs"):
09-May-201115:37:38org.apache.catalina.core.StandardContext
filterStartSEVERE:ExceptionstartingfilterJerseyFilter
com.sun.jersey.api.container.ContainerException:Fatalissuesfoundat
classnet.skybert.ws.RootResource.Seelogsformoredetails.
atcom.sun.jersey.server.impl.application.WebApplicationImpl.newResourceClass(WebApplicationImpl.java:552)
atcom.sun.jersey.server.impl.application.WebApplicationImpl.getResourceClass(WebApplicationImpl.java:517)
atcom.sun.jersey.server.impl.application.WebApplicationImpl.processRootResources(WebApplicationImpl.java:1153)
atcom.sun.jersey.server.impl.application.WebApplicationImpl.initiate(WebApplicationImpl.java:918)
atcom.sun.jersey.server.impl.application.WebApplicationImpl.initiate(WebApplicationImpl.java:589)
atcom.sun.jersey.spi.container.servlet.ServletContainer.initiate(ServletContainer.java:429)
atcom.sun.jersey.spi.container.servlet.ServletContainer$InternalWebComponent.initiate(ServletContainer.java:278)
atcom.sun.jersey.spi.container.servlet.WebComponent.load(WebComponent.java:566)
atcom.sun.jersey.spi.container.servlet.WebComponent.init(WebComponent.java:211)
atcom.sun.jersey.spi.container.servlet.ServletContainer.init(ServletContainer.java:333)
atcom.sun.jersey.spi.container.servlet.ServletContainer.init(ServletContainer.java:672)
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:
publicResponsegetSomeResponse(@QueryParam("first")StringpFirst,
StringpSecond){
^
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 ;-)