This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Hello, when we follow the Steps #1-#20 here on how to create an STS, on either Linux or Windows: https://jax-ws.dev.java.net/guide/Example_Applications.html#gfrlq We cannot see the WSDL as it says we should in Step #20 after we autodeploy onto GlassFish v3 from NetBeans. We have to manually deploy the WAR file into the GlassFish autodeploy directory in order to see the WSDL. Jiandong Guo of the Metro team has apparently also replicated this bug: http://old.nabble.com/Create-STS-with-Netbeans-6.8-and-Glassfish-V3-td27597150r0.html (Step #4) More info: http://old.nabble.com/Questions-on-creating-an-STS-with-NetBeans-td27588320r0.html (Item #2) This problem does not occur for normal JAX-WS webservices, for example the CalculatorService here: https://jax-ws.dev.java.net/guide/Developing_with_NetBeans.html#Creating_a_Web_Service
Was able to reproduce, however I don't see any difference in between the generated war file and the files being passed to autodeploy, thus reassigning for reavaluation to somebody who's more knowledgeable of how autodeploy works and what could be wrong. Maybe a bug in the GF implementation?
gmazza and/or mgrebac: could one of you attach the war file that appears to autodeploy correctly to this issue? It seems like this may end up getting filed against the server... but I will need to do some experiments first.
mgrebac: I cannot replicate the behavior, because the STS does not deploy... When I try to Build the project, I get syntax errors... similar to these... init: deps-module-jar: deps-ear-jar: deps-jar: wsimport-init: Created dir: /export/home/vkraemer/NetBeansProjects/MySTSProject5/build/generated-sources/jax-ws wsimport-service-MySTS: Created dir: /export/home/vkraemer/NetBeansProjects/MySTSProject5/build/generated/jax-wsCache/service/MySTS command line: wsimport -d /export/home/vkraemer/NetBeansProjects/MySTSProject5/build/generated/jax-wsCache/service/MySTS -extension -Xnocompile -Xendorsed -keep -s /export/home/vkraemer/NetBeansProjects/MySTSProject5/build/generated/jax-wsCache/service/MySTS -catalog /export/home/vkraemer/NetBeansProjects/MySTSProject5/catalog.xml -verbose /export/home/vkraemer/NetBeansProjects/MySTSProject5/src/conf/xml-resources/web-services/MySTS/wsdl/MySTSService.wsdl parsing WSDL... generating code... org/tempuri/MySTSService.java com/message/schemas/message/MessageBody.java com/message/schemas/message/ObjectFactory.java com/message/schemas/message/package-info.java Copying 4 files to /export/home/vkraemer/NetBeansProjects/MySTSProject5/build/generated-sources/jax-ws Copying 2 files to /export/home/vkraemer/NetBeansProjects/MySTSProject5/build/web/WEB-INF/wsdl/MySTS wsimport-service-generate: Created dir: /export/home/vkraemer/NetBeansProjects/MySTSProject5/build/web/WEB-INF/classes Created dir: /export/home/vkraemer/NetBeansProjects/MySTSProject5/build/web/META-INF Copying 1 file to /export/home/vkraemer/NetBeansProjects/MySTSProject5/build/web/META-INF Copying 4 files to /export/home/vkraemer/NetBeansProjects/MySTSProject5/build/web library-inclusion-in-archive: library-inclusion-in-manifest: Created dir: /export/home/vkraemer/NetBeansProjects/MySTSProject5/build/empty Compiling 5 source files to /export/home/vkraemer/NetBeansProjects/MySTSProject5/build/web/WEB-INF/classes /export/home/vkraemer/NetBeansProjects/MySTSProject5/src/java/org/me/my/sts/MySTS.java:23: package com.sun.xml.ws.security.trust.sts does not exist public class MySTS extends com.sun.xml.ws.security.trust.sts.BaseSTSImpl implements Provider<Source> { /export/home/vkraemer/NetBeansProjects/MySTSProject5/src/java/org/me/my/sts/MySTS.java:23: org.me.my.sts.MySTS is not abstract and does not override abstract method invoke(java.lang.Object) in javax.xml.ws.Provider public class MySTS extends com.sun.xml.ws.security.trust.sts.BaseSTSImpl implements Provider<Source> { /export/home/vkraemer/NetBeansProjects/MySTSProject5/src/java/org/me/my/sts/MySTS.java:28: cannot find symbol symbol : variable super location: class org.me.my.sts.MySTS return super.invoke(rstElement); /export/home/vkraemer/NetBeansProjects/MySTSProject5/build/generated-sources/jax-ws/org/tempuri/MySTSService.java:45: cannot find symbol symbol : constructor Service(java.net.URL,javax.xml.namespace.QName,javax.xml.ws.WebServiceFeature[]) location: class javax.xml.ws.Service super(__getWsdlLocation(), MYSTSSERVICE_QNAME, features); /export/home/vkraemer/NetBeansProjects/MySTSProject5/build/generated-sources/jax-ws/org/tempuri/MySTSService.java:53: cannot find symbol symbol : constructor Service(java.net.URL,javax.xml.namespace.QName,javax.xml.ws.WebServiceFeature[]) location: class javax.xml.ws.Service super(wsdlLocation, MYSTSSERVICE_QNAME, features); /export/home/vkraemer/NetBeansProjects/MySTSProject5/build/generated-sources/jax-ws/org/tempuri/MySTSService.java:61: cannot find symbol symbol : constructor Service(java.net.URL,javax.xml.namespace.QName,javax.xml.ws.WebServiceFeature[]) location: class javax.xml.ws.Service super(wsdlLocation, serviceName, features); 6 errors /export/home/vkraemer/NetBeansProjects/MySTSProject5/nbproject/build-impl.xml:413: The following error occurred while executing this line: /export/home/vkraemer/NetBeansProjects/MySTSProject5/nbproject/build-impl.xml:232: Compile failed; see the compiler error output for details. BUILD FAILED (total time: 3 seconds) Any advice on how to get beyond this point, so I can help you would be appreciated.
Vince, very common error--you need to place jaxws-api.jar and jaxb-api.jar from JAX-WS 2.2 [1] in your JRE endorsed directory. See 2.7.1.1 here: https://metro.dev.java.net/guide/Using_JAX_WS_2_x___Metro_1_x_2_0_with_Java_SE_6.html#Endorsed_directory HTH, Glen [1] https://jax-ws.dev.java.net/
Looks similar to this one: https://glassfish.dev.java.net/issues/show_bug.cgi?id=11501
This is it: https://glassfish.dev.java.net/issues/show_bug.cgi?id=11437 The above should be fixed already in GF trunk, so we should close this nb issue and mark it as a duplicate of the GF one.
verified that the trunk (v3.1) has this fix. the update release (v3.0.1 or v3u1) does not appear to have this fix.
This cannot be resolved by a plugin change. The resolution is to do the following... 1. push the change for https://glassfish.dev.java.net/issues/show_bug.cgi?id=11437 into the 3.0.1 branch 2. start bundling the v3.0.1 bits with the the dev build instead of the v3 bits. I guess that will require some schedule alignment discussions.
The schedule alignment discussions are already taking place, the plan is to bundle GF 3.0.1 with NetBeans 6.9. Not sure when we should start bundling dev builds of 3.0.1 in 6.9 dev - should it be ASAP, or is it fine to do it later (e.g. after 6.9 beta)?
(In reply to comment #9) > The schedule alignment discussions are already taking place, the plan is to > bundle GF 3.0.1 with NetBeans 6.9. Not sure when we should start bundling dev > builds of 3.0.1 in 6.9 dev - should it be ASAP, or is it fine to do it later > (e.g. after 6.9 beta)? We should include it ASA the fix to the GF issue is integrated into the 3.0.1 branch....
i just checked that the latest GF 3.0.1 promoted build has the fix for the server side of this issue. We need to bundle 3.0.1 promoted builds to finally resolve this issue. PetrJ: let me know when that happens and I will close this issue.
dev build 201004090201 includes GlassFish Server OSE 3.0.1