dev@glassfish.java.net

failed WS deployment is reported as success.

From: Gustav Trede <Gustav3d_devel_at_spray.se>
Date: Tue, 06 Feb 2007 14:12:48 +0100

I have had this problem for roughly 1 month , using latest nightly GFv2
and NB 5.5.1 builds , win xp jdk 1.6.
I have tried to get attention for this problem several times earlier.

while deploying j2ee ws module project from NB:
.......
schema update complete
JNDI InitialContext properties:{}
naming.bind
Cannot initialize endpoint : error is : null
java.lang.NullPointerException
      at
com.sun.xml.ws.model.wsdl.WSDLOperationImpl.freez(WSDLOperationImpl.java:133)
        at
com.sun.xml.ws.model.wsdl.WSDLPortTypeImpl.freeze(WSDLPortTypeImpl.java:77)
        at
com.sun.xml.ws.model.wsdl.WSDLBoundPortTypeImpl.freeze(WSDLBoundPortTypeImpl.java:206)
        at
com.sun.xml.ws.model.wsdl.WSDLModelImpl.freeze(WSDLModelImpl.java:227)
        at
com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.parse(RuntimeWSDLParser.java:208)
....(i cut of many exception lines here).....
        at
com.sun.enterprise.web.connector.grizzly.WorkerThreadImpl.run(WorkerThreadImpl.java:103)
LDR5010: All ejb(s) of [EJB_server_] loaded successfully!

The final GF status message and all status messages in NB says success.
But the WS does not work, fails to produce its WSDL file etc, so i
believe its crucial to have it correctly reported as such both in GF
itself and propagate it to NB.

regards
   gustav trede