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.
[build 20060308] I have a web service with serviceName attribute in annotation @WebService. The URL doesn't reflect this change.
It seems that websvc logical node in prj. view does not reflect correct name when constructing URL for test action (not only, some other actions suffer from this too) in case of JAX-WS2.0 ws. assume following entry in jax-ws.xml: <services> <service name="MyWebService"> <implementation-class>webservices.MyWebServiceImpl</implementation-class> </service> </services> it seems that URL is constructed from "name" attribute, but I think that something similar to following algorithm should be used instead: String urlPrefix = http://localhost:port/appname; String urlPart; if <implementation-class> is annotated with "@WebService(serviceName=...)" then urlPart = value of serviceName attribute in WebService annotation else urlPart = implementation-class name + "Service" return urlPrefix + urlPart
increasing to P2, see reason in my previous comment
Other influenced action is creation of wsclient for ws from other project.
the algorithm described above (regarding ws url construction) is correct for Java EE 5 apps, but not for J2EE 1.4 ones. There should be fallback to algorithm used for "Add to registry" action if called websvc resides in J2EE 1.4 project. We could also make the textfield next "project" combobox editable _after_ webservice selection to allow user to correct URL of websvc if the value suggested by IDE is incorrect. Current workaround is to copy&paste url between textfields, but this is not easy to find.
Implemented (for javaee5 WS) : http://websvc.netbeans.org/source/browse/websvc/core/src/org/netbeans/modules/websvc/core/jaxws/nodes/JaxWsNode.java?r1=1.1.2.11&r2=1.1.2.12 http://websvc.netbeans.org/source/browse/websvc/core/src/org/netbeans/modules/websvc/core/jaxws/nodes/JaxWsNode.java?r1=1.1.2.12&r2=1.1.2.13 Please, create the different issue if there is a problem with j2ee14 services.
v.