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 200804082140 (RC1), JDk1.6.0_05, Win Vista If I add JAX-WS web service to manager, it works O.K., node's created etc. If I add JAX-RPC web service, nothing happens at all (I have JAX-RPC plugin installed, use this URL: http://www.waterware.com/projects/samples/RouteMaster/wsdl/ ). There should be at least JAX-RPC client created.
Nam, can you take a look at this, please? Thanks.
The url has an ending '/' where the code expecting simply ending with 'wsdl' or 'WSDL'. Note, even removing the slash, the adding still fail because of some wsimport error.
yup, for this particular wsdl wsimport will always fail (since the WSDL is rpc/enc), but wscompile is able to handle such wsdl. The problem here is that wscompile is not run if wsimport fails (assuming one has JAXRPC plugin installed in the IDE). You can try also ie.: http://ws.soatrader.com/easycfm.com/1.0/Captcha?WSDL
Note: The first WSDL URL ends with "/" , but it still isn't problem for JAX-RPC web service client, for example (it's my testing WSDL and I use it over and over again with success). We can't consider this WSDL URL incorrect, when it works otherwise or there should be very clearly explained why exactly this WSDL URL doesn't work in manager by error message text.
Rico has kindly volunteered to fix this issue.
Since this is more complicated fix, than anticipated originally, changing SW to release61_fixes_candidate2.
The problem is that the WebServiceManager generates both the JAXWS (which comes first) and JAXRPC in the same vein. If JAXWS fails (such as in this case), all generation stops and JAXRPC is never generated, although it is possible to generate those artifacts. The specific WSDL problem here is that the WSDL is rpc/encoded which is not supported in JAXWS. Since we are using the JAXWS modeler to parse the WSDL (for both JAXWS and JAXRPC), no model is generated and everything fails. The solution is to separate the generation of JAXWS from JAXRPC so that the JAXRPC generation is not dependent on the WSDL model from JAXWS. This will require a re-write of WebServiceManager.addWebService().
Hello rcruz, can you please fix this bug as soon as possible (till 09-Jun-2008), so it can be part of NB 6.1 patch 2? Thanks!
The issue didn't meet nomination criteria for 61patch2 till nomination cut-off date. It has been moved to the next patch.
This issue did not meet the criteria for inclusion in NetBeans 6.1 Patch 3.
*** Issue 132454 has been marked as a duplicate of this issue. ***
Fixed.
v.