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: Netbeans 5.0 build dated 10/12/2005 Build and Deploy a webservice in to the SJSAS 8.0 UR2 App. Server. Now try "Adding to Registry" using the webservices node under the webservice project. THe following error message keeps showing up even though the App. server is confirmed to be running. "Unable to add web service to registry. Make sure it is deployed, the server is running and the correct WSDL was entered" I verified that the wsdl was accessinble through the http://localhost:8080 and can see the WSDL page. This proves that the WSDL was deployed and the server is running. However "Adding to registry" fails even after multiple attempts. Due to this the WS client cannot be developed to access the service. I am unable to test the added WS operations due to this problem.
I checked Balaji's install of NetBeans and the webservices registry module failed to initialize (displayed w/ red X and message "Press F1 for help"), but there were no messages in the log. Also, when F1 was pressed, the IDE window disppeared and we had to kill the NB process via TaskManager (this is bad, IMO). So the problem here is solved by figuring out why the registry did not initialize. He had spaces in both the NetBeans install dir and user dir paths, so I asked him to install a second copy that did not do either and try that. In the meantime, I'm going to test a similar install (w/ the spaces, etc.) and see if I can reproduce the problem. It could also be a path length issue somewhere (this was on Windows XP).
Disregard previous comment, this problem is independent of spaces in any paths. I was able reproduce this problem with my recent personal dev build by running on JDK 1.4.2 (rev. 05). Balagi was using rev. 09, so that portion probably doesn't matter. Raising priority to P2.
I noticed that the description for an invalid registry node indicates that when running under JDK 1.4.2, an additional XML library is needed, so this is why the node is broken. I'm leaving this as an open P2 though, for two reasons: 1) This description message is only visible if you can view properties on the node. But (a) there is no popup menu provided on the disabled node, so no quick access to properties and (b) you can view properties globally by using Windows | Properties, then reselected the disabled web service registry node, but no customer is going to do that. I only did it AFTER I'd seen the text in the source code bundle. 2) F1 for help killed the NB window (but not NB - weird) on Balaji's machine. On my machine, I got the message "[org.netbeans.modules.javahelp] Warning: the JavaHelp topic ID org.netbeans.modules.websvc.registry.netbeans.WebServices RootNodeInterface was not found." twice in the console window, so there is a bug here wrt/ help. 3) At least for dev builds, there is no JAXRPC-16 library on the dev update center. (It is there when running 5.0 beta though.) Not sure how important this problem is, but as a dev build user, I have no idea right now how to obtain this library, so I can't test under 1.4.2. I think the solution for this problem needs to be far more visible. Otherwise it'll be a support nightmare when 5.0 is released.
*** Issue 66411 has been marked as a duplicate of this issue. ***
I think this definitely needs a cleaner solution. We can't move to JDK 1.5 because it breaks some integration projects. Maybe the web service supporting module can indicate the missing libs when F1 is hit. if I remember, hitting F1 does absolutely nothing useful right now anyway. This should be cleaned up before release.
rnovak, could you put JAXRPC-16 library also on dev update center, please? For more info see #3 in last pcw's comment. Thanks.
This should be also announced in Release notes: Install the JAXRPC-16 library to enable the WS support in JDK 1.4.2 The good news is that you don't need to have the SJS application server installed for WS clients in java project and for WS Registry.
See also my #2 above. Ignore the "F1 killed NB" comment, it was a workspace switcher the user had installed. But the invalid help context bug has to be fixed by release. If we show text that says "Hit F1", hitting F1 w/ that node selected has to take the user directly to the explanation on how to fix it.
Seams that JAXRPC-16 library exists on dev update center. Changed text for disabled WS Registry node to : "Web Services[disabled]-press F1 for help" See : http://websvc.netbeans.org/source/browse/websvc/registry/src/org/netbeans/modules/websvc/registry/netbeans/Bundle.properties?r1=1.8&r2=1.9 Geertjan, please, implement the Help Id for org.netbeans.modules.websvc.registry.netbeans.WebServicesRootNodeInterface and mention the problem in Realease Notes.
Fixed. Please verify.
I've also passed on this text to Talley, to put in the Release Notes: "If you use JDK 1.4.2 and you want to work with web services, install the JAXRPC-16 library from the Update Center." Please verify that this is correct.
v.