Rama Pulavarthi's Blog

Rama Pulavarthi is a Member of Technical Staff in the Java Web Services group at Sun Microsystems. He currently works on the development of JAX-WS Reference Implementation. He has previously lead the Software Quality Engineering effort of JAX-RPC. He holds a Masters degree in Computer Science from Auburn University in Alabama and Bachelors in Electronics and Communication from JNTU Hyderabad.

Speaking at JavaOne 2009 on JAX-WS 2.2

JAX-WS 2.1.6 in JDK 6u14

JAX-WS Maven 2 Plugin 1.12 released

JAX-WS Maven2 plugin 1.12 is released which has some bug fixes related to configuring the wsimport/wsgen options and minor usability issue. JAX-WS maven plugin 1.12 depends on recently released JAX-WS RI 2.1.7. Along with other changes in JAX-WS RI 2.1.7, For maven users it has one important bug fix related to the dependency on the woodstox.

Just a recap on the previous 1.11 release, If you have n't noticed, In 1.11 wsimport goal default behavior is changed to not compile the generated sources. This was fixed as JAX-WS-COMMONS-25.

• JAX-WS-COMMONS-36: wsgen extension option is not working with the maven plugin.
• JAX-WS-683: Confusing Warning "Nothing to do, no WSDL found!" with wsimport goal.

You can find more about the plugin usage at jax-ws commons project. Do let us know if you see any issues with using the maven plugin.

Tip for using JAX-WS 2.2/ Metro 2.0 with Tomcat 6.x on JDK 6

If you trying to use JAX-WS 2.2 on top of JDK 6, you run into classloading problems. Resonating with the problems we had with using JAX-WS 2.1 on JDK 6 FCS?, Dejavu !!!.

As you guessed, JDK 6 (U4 and later) has JAX-WS implementation with JAX-WS 2.1 API. If you try to use JAX-WS 2.2, the runtime always picks up the JAX-WS API from bootclasloader and will not see JAX-WS 2.2 API in your classpath. Well, the solution is the same, i.e, using the endorsed overriding mechanism. This has been documented and discussed before.

But how do you configure for Web Services running on Tomcat 6 using JDK 6. Its easy with Tomcat 5.5, you just need to copy jaxws-api.jar and jaxb-api.jar into $TOMCAT_HOME/common/endorsed directory. But there are some changes in classloading in Tomcat 6.x and there is no documentation on the default endorsed directory.

Here it is, you have to create endorsed directory in $TOMCAT_HOME and Copy jax-ws.api.jar and jaxb-api.jar from JAX-WS (webservices-api.jar in case of Metro) to $TOMCAT_HOME/endorsed. You might also find my other blog on running JAX-WS samples on Tomcat 6.x useful.

I am putting here one of the problems one would see when using JAX-WS 2.2 features without endorsed mechanism. For ex, if you are using AddressingFeature.Responses added in JAX-WS 2.2 API, you would get
SEVERE: WSSERVLET11: failed to parse runtime descriptor: java.lang.NoSuchMethodError: javax.xml.ws.soap.Addressing.responses()Ljavax/xml/ws/soap/AddressingFeature$Responses; java.lang.NoSuchMethodError: javax.xml.ws.soap.Addressing.responses()Ljavax/xml/ws/soap/AddressingFeature$Responses;

Follow the above tip to configure the endorsed directory and it should work.

Technorati:
JAX-WS
Tomcat 6

June 2009

Search this blog:

Categories

Archives

June 2009
April 2009
March 2009
February 2009
November 2008
October 2008
August 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
October 2007
September 2007
July 2007
June 2007
February 2007
January 2007
September 2006
August 2006
June 2006
May 2006
April 2006

Recent Entries

Speaking at JavaOne 2009 on JAX-WS 2.2

JAX-WS 2.1.6 in JDK 6u14

JAX-WS Maven 2 Plugin 1.12 released

This work is licensed under a Creative Commons License.