Home/ Questions/Q 185095
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-11T15:24:33+00:00

I’ve deployed Jersey on Tomcat and everything works perfectly (when I use the com.sun.jersey.spi.container.servlet.ServletContainer),

  • 0

I’ve deployed Jersey on Tomcat and everything works perfectly (when I use the com.sun.jersey.spi.container.servlet.ServletContainer), but as soon as I change it to the com.sun.jersey.spi.spring.container.servlet.SpringServlet (according to all the tutorials I can find), I get a nasty exception:

Apr 19, 2009 5:07:35 PM org.apache.catalina.core.ApplicationContext log INFO: Marking servlet ServletAdaptor as unavailable Apr 19, 2009 5:07:35 PM org.apache.catalina.core.StandardContext loadOnStartup SEVERE: Servlet /myservice threw load() exception java.lang.ClassNotFoundException: com.sun.jersey.spi.service.ComponentProvider

Any idea what package/distribution it can reside? What am I missing?

May be I don’t need it at all. I’m trying to make sure that when my resource class is loaded it’ll be Autowired and initialized with the rest of the Beans it depends on. Can it be done differently?

Thanks.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. The com.sun.jersey.spi.service.ComponentProvider interface is part of the jersey-core JAR so it’s odd that you’re getting that exception.

    Make sure you’re using the same version of the jersey libraries together (i.e. you’re using Jersey 1.0.1 libraries, not mixing 1.0 and 1.0.1 as the Spring classes got renamed between those two releases).

    Also ensure you have a ContextLoaderListener in your web.xml like so:

    <listener>     <listener-class>org.springframework.web.context.ContextLoaderListener</listener-class> </listener>
    • 0