I have an application that acts as a client for a RESTful WS. This application 
uses jersey-client (1.18.1) to make the WS calls.
This application fails to load on TomEE+ 1.7.0-SNAPSHOT with the following 
error:

———————————————————————————
Caused by: java.lang.ClassNotFoundException: 
com.sun.jersey.core.util.FeaturesAndProperties
at 
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1720)
at 
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1571)
at 
org.apache.tomee.catalina.LazyStopWebappClassLoader.loadClass(LazyStopWebappClassLoader.java:129)
... 34 more
———————————————————————————

I dug a little deeper into the class loading logic and it seems that TomEE will 
not load the jersey-core that is required by jersey-client because 
jersey-core.jar contains some classes that should not be deployed as part of a 
javaEE application.

Namely, it contains javax.ws.rs.Path, but doesn’t contain 
javax.ws.rs.core.Configurable, so the jar is ignored by the 
LazyStopWebappClassLoader.

Does this mean, I am not supposed to have jersey-client as part of my web app? 
If so - what would you recommend as a replacement?
Or is this just something that might be fixed on the TomEE-side? Please advise.

Thanks in advance,
Markus

--
Markus Frisch
[Prokurist / Authorized Representative]
nobisCum Deutschland GmbH

[T] +49 9302 / 987 97 - 2633
[M] +49 173 / 91 88 058
[@] [email protected]<mailto:[email protected]>
[URL] http://www.nobisCum.de

[Anschrift] Ostring 2-4, 97228 Rottendorf, Germany
[Registergericht] Würzburg, HRB 5159
[Geschäftsführer] Herbert Stieglitz, Hans-Peter Holl










Reply via email to