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 93250 - Drag N Drop of WSDL with partnerlinktype doesnt populate the role in the PartnerLink Dialog
Summary: Drag N Drop of WSDL with partnerlinktype doesnt populate the role in the Part...
Status: VERIFIED DUPLICATE of bug 91588
Alias: None
Product: soa
Classification: Unclassified
Component: BPEL (show other bugs)
Version: 5.x
Hardware: Other Windows XP
: P1 blocker (vote)
Assignee: issues@soa
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-01-26 01:07 UTC by Shivanand Kini
Modified: 2007-02-05 19:22 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
ScreenShot of the bpel editor and Partnerlink dialog (72.82 KB, image/png)
2007-01-26 01:08 UTC, Shivanand Kini 		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 Shivanand Kini 2007-01-26 01:07:30 UTC 
1. Create a BPEL Module
2. Create a New WSDL Document in the process files.
3. Select SOAP on the last step of the wizard (all previous ones click Next)
and then click Finish
4. WSDL File is created.
5. Create a new BPEL Document.
6. Drag and Drop the created WSDL File into the BPEL editor canvas.
7. The add partnerlinktype dialog pops up.

Observation: The role is not populated, even though the wsdl file has a role
defined for the partnerlinktype.

Expectation: The roles are shown.

Current ugly workaround:
1. Create a new partnerlink in the dialog
2. Delete the newly created partnerlink (not the wrapper.wsdl created)
3. Drag and Drop the first wsdl file again
4. Sometimes the role is shown.
5. Sometimes select the other partnerlinktype and select the one you want, the
roles show up.
Comment 1 Shivanand Kini 2007-01-26 01:08:02 UTC 
Created attachment 37692 [details]
ScreenShot of the bpel editor and Partnerlink dialog
Comment 2 Mikhail Kondratyev 2007-01-26 05:15:11 UTC 
This is a duplicate of issue 91588
Please check and reopen this bug if you disagree.

Developers have fixed this already and the functionality should work in the
latest build.

*** This issue has been marked as a duplicate of 91588 ***
Comment 3 Shivanand Kini 2007-02-05 19:22:29 UTC 
Verified on build from code of Feb 05, 2006.