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 94206 - Should add "Customize WSDL Import" item in contextual menu
Summary: Should add "Customize WSDL Import" item in contextual menu
Status: VERIFIED FIXED
Alias: None
Product: xml
Classification: Unclassified
Component: WSDL Tools (show other bugs)
Version: 5.x
Hardware: All All
: P2 blocker (vote)
Assignee: Nathan Fiedler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-02-03 01:02 UTC by _ hong_lin
Modified: 2007-02-28 19:55 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

Attachments
WSDL files used in 2nd scenario (2.96 KB, application/octet-stream)
2007-02-06 22:02 UTC, jlautz 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description _ hong_lin 2007-02-03 01:02:28 UTC 
Build: Gavotte daily build 070131_27

Right now, if A.wsdl file imported B.wsdl file, and then B.wsdl is moved to
another project. A broken issue would be detected by validating A.wsdl.

Right click the broken import item, there isn't a "Customize" menu item. What
user has to do now is to delete the broken import item, than add it again.

It would be good to have the "Customize" feature.So user can fix the issue in
one step.
Comment 1 Nathan Fiedler 2007-02-03 01:45:55 UTC 
Fixed in release551 branch.

wsdlui/src/org/netbeans/modules/xml/wsdl/ui/view/treeeditor/WSDLElementNode.java;
new revision: 1.1.2.26.4.6; previous revision: 1.1.2.26.4.5
wsdlui/src/org/netbeans/modules/xml/wsdl/ui/view/treeeditor/WSDLImportNode.java;
new revision: 1.1.2.9.8.1; previous revision: 1.1.2.9
Comment 2 jlautz 2007-02-06 21:55:06 UTC 
Seen on Windows XP with Gavotte build 070206 and JDK 1.5.0_10:

1. Add the attached WSDL files to a BPEL project. newWSDL.wsdl imports
newWSDL3.wsdl. We will use newWSDL4.wsdl later.
2. Delete the newWSDL3 file from the Projects window.
3. Validate the newWSDL.wsdl file. There will be validation errors.
4. Right-click the newWSDL3 and choose Customize.
5. In the WSDL Import Customizer dialog, choose newWSDL4.wsdl, and click OK.
==> Note that the name on the WSDL import node is still newWSDL3.wsdl.

I think the name should be changed to reflect the name of the newly-imported file.
Comment 3 jlautz 2007-02-06 21:56:07 UTC 
(In case the above wasn't clear, I think this bug wasn't quite fixed in its
entirety. If you think this is a new bug, let me know.)
Comment 4 jlautz 2007-02-06 22:02:28 UTC 
Created attachment 38149 [details]
WSDL files used in 2nd scenario
Comment 5 jlautz 2007-02-06 22:06:01 UTC 
One more observation: if I shutdown and restart NB, the node for the imported
WSDL  then has the name of the wsdl file we imported in Step 5.
Comment 6 jlautz 2007-02-06 22:26:02 UTC 
Returning to fixed status. The enhancement has been added.
Comment 7 jlautz 2007-02-06 22:27:16 UTC 
Verified on Windows XP with Gavotte build 070206 and JDK 1.5.0_10. Customize is
now in the context menu for a WSDL import node. 

There is a bug on this feature, logged as issue 94206.