I am running Jersey 1.0.1 on TomCat 6 on JDK 1.6.0_11 without any problems.
Regards
Markus
> -----Original Message-----
> From: sarat.pediredla [mailto:sarat.pediredla_at_gmail.com]
> Sent: Donnerstag, 19. Februar 2009 19:14
> To: users_at_jersey.dev.java.net
> Subject: [Jersey] Jersey 1.0 on Tomcat 6 with JDK 6 does not run
>
>
> Hi,
>
> I have a Jersey enabled application that is deployed on Tomcat 6. I
> have had
> no problems running this in JDK 5 but a recent JDK update to 6 is now
> breaking everything. The error I get is as follows,
>
> <code>
> Caused by: java.lang.NoClassDefFoundError: Could not initialize class
> com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder
> at
> com.sun.xml.bind.v2.runtime.JAXBContextImpl.getTypeInfoSet(JAXBContextI
> mpl.java:432)
> at
> com.sun.xml.bind.v2.runtime.JAXBContextImpl.<init>(JAXBContextImpl.java
> :297)
> at
> com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:13
> 9)
> at
> com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:11
> 7)
> at sun.reflect.GeneratedMethodAccessor246.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccesso
> rImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:210)
> at javax.xml.bind.ContextFinder.find(ContextFinder.java:368)
> at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:574)
> at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:522)
> at
> com.sun.jersey.impl.provider.entity.AbstractJAXBProvider.getStoredJAXBC
> ontext(AbstractJAXBProvider.java:194)
> at
> com.sun.jersey.impl.provider.entity.AbstractJAXBProvider.getJAXBContext
> (AbstractJAXBProvider.java:172)
> at
> com.sun.jersey.impl.provider.entity.AbstractJAXBProvider.getMarshaller(
> AbstractJAXBProvider.java:158)
> at
> com.sun.jersey.impl.provider.entity.AbstractJAXBProvider.getMarshaller(
> AbstractJAXBProvider.java:131)
> at
> com.sun.jersey.impl.provider.entity.AbstractRootElementProvider.writeTo
> (AbstractRootElementProvider.java:110)
> at
> com.sun.jersey.spi.container.ContainerResponse.write(ContainerResponse.
> java:251)
> at
> com.sun.jersey.impl.application.WebApplicationImpl.handleRequest(WebApp
> licationImpl.java:752)
> at
> com.sun.jersey.impl.application.WebApplicationImpl.handleRequest(WebApp
> licationImpl.java:692)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletCo
> ntainer.java:344)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applic
> ationFilterChain.java:290)
> ... 91 more
> </code>
>
> A search on Google reveals nothing except the fact that the Java 6 is
> suspect in some way? Or is this a problem with the JAXB implementation
> and
> version? Any help appreciated.
> --
> View this message in context: http://n2.nabble.com/Jersey-1.0-on-
> Tomcat-6-with-JDK-6-does-not-run-tp2354538p2354538.html
> Sent from the Jersey mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jersey.dev.java.net
> For additional commands, e-mail: users-help_at_jersey.dev.java.net