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 106320 - operation nodes are not created for JAXRPC ws from wsdl
Summary: operation nodes are not created for JAXRPC ws from wsdl
Status: RESOLVED WONTFIX
Alias: None
Product: webservices
Classification: Unclassified
Component: JAX-RPC (show other bugs)
Version: 6.x
Hardware: All All
: P4 blocker (vote)
Assignee: Milan Kuchtiak
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-06-11 21:09 UTC by Lukas Jungmann
Modified: 2009-12-21 05:58 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
ws nodes (127.34 KB, image/png)
2007-06-11 21:09 UTC, Lukas Jungmann
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Lukas Jungmann 2007-06-11 21:09:16 UTC
-create new JAXRPC ws in J2EE 1.4 webproject and some operation in it
-create new JAXRPC ws from wsdl in it
-expand ws nodes in project view

=> for ws from java one can see nodes for its operations, for ws from wsdl one
can't (see attached picture) - the behaviour should be consistent
Comment 1 Lukas Jungmann 2007-06-11 21:09:56 UTC
Created attachment 43526 [details]
ws nodes
Comment 2 bhate 2007-09-28 19:53:21 UTC
the logic for from wsdl case is not implemented yet in jaxrpc support WsbServiceChildren. targeting 6.0 FCS.
Comment 3 bhate 2008-02-19 22:19:59 UTC
The current behavior is consistent with Netbeans 5.x. So this seems like enhancement. making P4.
Comment 4 Lukas Jungmann 2008-04-14 17:13:12 UTC
moving opened issues where TM != dev to TM=TBD
Comment 5 Milan Kuchtiak 2008-12-01 15:06:03 UTC
Still valid.
Comment 6 Quality Engineering 2009-12-21 05:58:15 UTC
This bug was reported against NetBeans IDE 6.0 or an older release, or against a non-maintained module. NetBeans team does not have enough resources to get to this issue, therefore we are closing the issue as a WONTFIX. If you are interested in providing a patch for this bug, please see our NetFIX guidelines for how to proceed. 

We apologize for any inconvenience.


Thank you.
The NetBeans Team