Simple JAX-WS web service does not work on WS7u6

Question

Hello,
I am trying to deploy a very simple JAX-WS web service on WS7u6, but it is not working. The same service deployed on Tomcat 6.0.16 works fine.
The service I'm trying to deploy is from a tutorial on the Netbeans website: [http://netbeans.org/kb/docs/websvc/jax-ws.html] - it is a simple calculator web service that adds two ints and returns an int.
I follow the tutorial to the letter, but when I attempt to deploy on WS7, it fails as follows:
[10/Dec/2009:21:21:44] info (25757): CORE3276: Installing a new configuration
[10/Dec/2009:21:21:44] info (25757): WEB0118: SSO is enabled in virtual server [dadydude.qisc.com]
[10/Dec/2009:21:21:44] info (25757): WEB0100: Loading web module in virtual server [dadydude.qisc.com] at [/wstest]
[10/Dec/2009:21:21:44] info (25757): WSSERVLET12: JAX-WS context listener initializing
[10/Dec/2009:21:21:44] info (25757): wsdl cannot be found from DD or annotation. Will generate and publish a new WSDL for SEI endpoints.
[10/Dec/2009:21:21:44] failure (25757): WSSERVLET11: failed to parse runtime descriptor: class: org.me.calculator.jaxws.Add could not be found
class: org.me.calculator.jaxws.Add could not be found
     at com.sun.xml.ws.modeler.RuntimeModeler.getClass(RuntimeModeler.java:271)
     at com.sun.xml.ws.modeler.RuntimeModeler.processDocWrappedMethod(RuntimeModeler.java:562)
     at com.sun.xml.ws.modeler.RuntimeModeler.processMethod(RuntimeModeler.java:509)
     at com.sun.xml.ws.modeler.RuntimeModeler.processClass(RuntimeModeler.java:355)
     at com.sun.xml.ws.modeler.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:251)
     at com.sun.xml.ws.server.RuntimeEndpointInfo.createSEIModel(RuntimeEndpointInfo.java:170)
     at com.sun.xml.ws.server.RuntimeEndpointInfo.init(RuntimeEndpointInfo.java:317)
     at com.sun.xml.ws.transport.http.servlet.WSServletContextListener.createModelAndMetadata(WSServletContextListener.java:200)
     at com.sun.xml.ws.transport.http.servlet.WSServletContextListener.contextInitialized(WSServletContextListener.java:120)
     at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4456)
     at org.apache.catalina.core.StandardContext.start(StandardContext.java:5113)
     at com.sun.webserver.connector.nsapi.WebModule.start(WebModule.java:235)
     at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1224)
     at org.apache.catalina.core.StandardHost.start(StandardHost.java:924)
     at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1224)
     at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:520)
     at org.apache.catalina.startup.Embedded.start(Embedded.java:917)
     at com.sun.enterprise.web.PwcWebContainer.onStartup(PwcWebContainer.java:70)
     at com.sun.webserver.connector.nsapi.WebContainer.start(WebContainer.java:491)
     at com.sun.webserver.init.J2EERunner.confPostInit(J2EERunner.java:304)
[10/Dec/2009:21:21:44] failure (25757): WebModule[/wstest]PWC1275: Exception sending context initialized event to listener instance of class com.sun.xml.ws.transport.http.servlet.WSServletContextListener
WSSERVLET11: failed to parse runtime descriptor: class: org.me.calculator.jaxws.Add could not be found
     at com.sun.xml.ws.transport.http.servlet.WSServletContextListener.contextInitialized(WSServletContextListener.java:131)
     at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4456)
     at org.apache.catalina.core.StandardContext.start(StandardContext.java:5113)
     at com.sun.webserver.connector.nsapi.WebModule.start(WebModule.java:235)
     at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1224)
     at org.apache.catalina.core.StandardHost.start(StandardHost.java:924)
     at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1224)
     at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:520)
     at org.apache.catalina.startup.Embedded.start(Embedded.java:917)
     at com.sun.enterprise.web.PwcWebContainer.onStartup(PwcWebContainer.java:70)
     at com.sun.webserver.connector.nsapi.WebContainer.start(WebContainer.java:491)
     at com.sun.webserver.init.J2EERunner.confPostInit(J2EERunner.java:304)
Caused by: class: org.me.calculator.jaxws.Add could not be found
     at com.sun.xml.ws.modeler.RuntimeModeler.getClass(RuntimeModeler.java:271)
     at com.sun.xml.ws.modeler.RuntimeModeler.processDocWrappedMethod(RuntimeModeler.java:562)
     at com.sun.xml.ws.modeler.RuntimeModeler.processMethod(RuntimeModeler.java:509)
     at com.sun.xml.ws.modeler.RuntimeModeler.processClass(RuntimeModeler.java:355)
     at com.sun.xml.ws.modeler.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:251)
     at com.sun.xml.ws.server.RuntimeEndpointInfo.createSEIModel(RuntimeEndpointInfo.java:170)
     at com.sun.xml.ws.server.RuntimeEndpointInfo.init(RuntimeEndpointInfo.java:317)
     at com.sun.xml.ws.transport.http.servlet.WSServletContextListener.createModelAndMetadata(WSServletContextListener.java:200)
     at com.sun.xml.ws.transport.http.servlet.WSServletContextListener.contextInitialized(WSServletContextListener.java:120)
     ... 11 more
[10/Dec/2009:21:21:44] failure (25757): PWC1306: Startup of context /wstest failed due to previous errors
[10/Dec/2009:21:21:44] failure (25757): Null component com.sun.web-3:type=JspMonitor,name=jsp,WebModule=//localhost/wstest,J2EEApplication=null,J2EEServer=none
[10/Dec/2009:21:21:44] info (25757): CORE3280: A new configuration was successfully installed
[10/Dec/2009:21:21:44] info (25757): WSSERVLET13: JAX-WS context listener destroyedAm I simply missing something obvious here?
Thanks,
Bill

Answer 1

OK, I've made significant progress.
As I suspected, JAX-WS was indeed supposed to generate the missing class for me, but while it appears to do so automatically when deploying in Tomcat, it is necessary to hack your build.xml file to add the generated classes to your WAR file for WS7. Reference [http://developers.sun.com/webtier/reference/techart/websvcs_nb.html] for a (rather dated) description of how to deploy a JAX-WS service on WS7 (using Netbeans 5.0!).
Note that as of NB6.7/6.8 much of the manual process is now done automatically by Netbeans, but curiously, not the part that actually causes the web service code to be generated. For that, we have to manually modify the build.xml to include a "-pre-dist" target that invokes the wsgen Ant task.
This is the target I added to build.xml for this sample calculator service:
  <target name="-pre-dist">
    <taskdef name="wsgen" classname="com.sun.tools.ws.ant.WsGen">
      <classpath path="${javac.classpath}:${j2ee.platform.classpath}"/>
    </taskdef>
    <wsgen
      debug="true"
      keep="true"
      destdir="build/web/WEB-INF/classes"
      resourcedestdir="build/web/WEB-INF/classes"
      xendorsed="true"
      sei="org.me.calculator.CalculatorWS">
      <classpath>
        <pathelement path="${javac.classpath}:${j2ee.platform.classpath}"/>
        <pathelement location="${java.home}/../lib/tools.jar"/>
        <pathelement location="build/web/WEB-INF/classes"/>
      </classpath>
    </wsgen>
  </target>That will allow the project to build and deploy successfully, and I am now able to view my WSDL.
However, at first the service itself was not working. After a bit of casting about, I determined that this was due to the fact that at some point I had added the METRO library to the project rather than simply the JAX-WS 2.2 library. After returning the configuration to just use JAX-WS and doing a clean build and deploy, the simple web service now works!
One thought does emerge from all this, though: if the built in support for Tomcat runs wsgen for me when I deploy an app to that container, perhaps the Sun WS7 team needs to update their Netbeans plugin to do this for us, too. I should probably open a support case on that...
OK, now on to real work. ;-)
Bill