If you have an application that uses jersey-client in any way then it may fail with an error along the lines of:
Caused by: java.lang.ClassNotFoundException: com.sun.jersey.core.util.FeaturesAndProperties at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java) at org.apache.tomee.catalina.LazyStopWebappClassLoader.loadClass(LazyStopWebappClassLoader.java) ... 34 more
This is due to the fact that the jersey-core.jar contains some classes that should not be deployed as part of a javaEE application. For example, it contains javax.ws.rs.Path but does not contain javax.ws.rs.core.Configurable, so the jar is usually ignored by TomEE.
You could switch to using the Apache CXF Client, which is what we would recommend. If you really want to keep Jersey then you can use set the following property in your [TomEE]\conf\system.properties
This will then allow Jersey classes to be loaded by TomEE (After a restart).
All edits are reviewed before going live, so feel free to do much more than fix typos or links. If you see a page that could benefit from an entire rewrite, we'd be thrilled to review it. Don't be surprised if we like it so much we ask you for help with other pages :)NOTICE: unless indicated otherwise on the pages in question, all editable content available from apache.org is presumed to be licensed under the Apache License (AL) version 2.0 and hence all submissions to apache.org treated as formal Contributions under the license terms.