On Aug 21, 2013, at 6:18 AM, Michael Südkamp <michael.suedk...@docware.de> wrote:
> Hello, > > My problem is not directly related to Tomcat but to any web container... > > A while ago we developed a webservice interface to our Java web-app. At that > time we needed Java 5 compatibility, that's why we used the JAX-WS RI 2.2.5 > package. > Now we increased the system requirement for our web-app to Java 6 and thus we > thought it should be could idea to let our webservice rely on the JAVA 6 > built-in JAX-WS. But we ran into problems. > First we realized that using the > com.sun.xml.ws.transport.http.servlet.WSServletContextListener in Tomcat > web.xml still requires the jaxws-rt.jar from the JAX-WS RI package (class is > in there). So we readded several JARs from the JAX-WS RI to our web-app until > the Listener worked. > But then we realized that the classes in jaxws-rt-jar overlap somehow with > the built-in Java classes, i.e. we get NoSuchMethod errors now. Depending on what libraries you are trying to add, you might need to use the JVM's endorsed mechanism. See this link for more info. http://docs.oracle.com/javase/6/docs/technotes/guides/standards/ See this link if you are deploying on Tomcat. https://tomcat.apache.org/tomcat-7.0-doc/class-loader-howto.html#XML_Parsers_and_Java > Now my question: what is the preferred way to achieve what we need. Should we > go back to the external JAX-WS RI package? Internal / external, it's just a matter of preference and what works for your app. The internal (i.e. bundled with the JVM) classes are more convenient to use, but you have no choice as to the version you get. With external JARs you can use a specific version, often more recent than what is bundled with the JVM. Dan --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
