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.

Bug 132412 - Nothing happens if add JAX-RPC web service
Summary: Nothing happens if add JAX-RPC web service
Alias: None
Product: webservices
Classification: Unclassified
Component: Manager (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: Roderico Cruz
Keywords: RELNOTE
Depends on:
Reported: 2008-04-09 14:55 UTC by Jaroslav Pospisil
Modified: 2008-09-11 15:59 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description Jaroslav Pospisil 2008-04-09 14:55:36 UTC
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: ).
There should be at least JAX-RPC client created.
Comment 1 Lukas Jungmann 2008-04-21 20:01:38 UTC
Nam, can you take a look at this, please?

Comment 2 Nam Nguyen 2008-04-21 21:23:06 UTC
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.
Comment 3 Lukas Jungmann 2008-04-21 22:03:11 UTC
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.:
Comment 4 Jaroslav Pospisil 2008-04-22 13:30:03 UTC
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.
Comment 5 Peter Liu 2008-04-23 18:58:31 UTC
Rico has kindly volunteered to fix this issue.
Comment 6 Jaroslav Pospisil 2008-04-24 09:05:21 UTC
Since this is more complicated fix, than anticipated originally, changing SW to release61_fixes_candidate2.
Comment 7 Roderico Cruz 2008-04-24 18:06:54 UTC
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().
Comment 8 pslechta 2008-06-03 13:40:31 UTC
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?

Comment 9 pgebauer 2008-06-13 10:23:51 UTC
The issue didn't meet nomination criteria for 61patch2 till nomination cut-off
date. It has been moved to the next patch.
Comment 10 rbalada 2008-08-06 15:59:16 UTC
This issue did not meet the criteria for inclusion in NetBeans 6.1 Patch 3.
Comment 11 Roderico Cruz 2008-08-12 20:44:01 UTC
*** Issue 132454 has been marked as a duplicate of this issue. ***
Comment 12 Roderico Cruz 2008-09-08 07:19:11 UTC
Comment 13 Jaroslav Pospisil 2008-09-11 15:59:47 UTC