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 85416 - WSDL Extensibility elements & Correlation Keys
Summary: WSDL Extensibility elements & Correlation Keys
Status: RESOLVED DUPLICATE of bug 88318
Alias: None
Product: soa
Classification: Unclassified
Component: BPEL (show other bugs)
Version: 5.x
Hardware: All All
: P1 blocker (vote)
Assignee: mfoster
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-09-21 09:51 UTC by mfoster
Modified: 2008-01-24 13:25 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments
BPEL Aansluting Project (82.71 KB, application/octet-stream)
2006-09-22 21:34 UTC, mfoster
Details
CA Aansluiting Project (327.32 KB, application/octet-stream)
2006-09-22 21:34 UTC, mfoster
Details
BPEL Aansluting Project (82.71 KB, application/octet-stream)
2006-09-24 17:40 UTC, mfoster
Details
CA Aansluiting Project (327.32 KB, application/octet-stream)
2006-09-24 17:40 UTC, mfoster
Details

Note You need to log in before you can comment on or make changes to this bug.
Description mfoster 2006-09-21 09:51:54 UTC
Not sure if this is planned, but we need a wizard for Alias in order to take 
the pain out of creating correlation keys.

Note that at the moment we manually add the details to a WSDL. It may be that 
the correlation key is made up of elements from more than one WSDL hence we 
need to be careful were we put the Alias.

My suggestion would be to automatically create a wrapper wsdl with a name of 
something like ProjectExtensibilityElements.wsdl and create the Alias etc in 
here, each project could have one of these WSDLs if required.

I would also suggest this may be a good place to put the Partner Link stuff as 
well (as opposed to tagging it on to the end of one of my imported WSDLs).
Comment 1 mfoster 2006-09-21 10:02:57 UTC
At the moment in order to create a correlation key you need to manually add 
Alias details to the project either in an existing imported WSDL or in a 
wrapper type WSDL.

This should be automated with a wizard in the same manner as the PL wizard.

We should be very careful where we add the Alias details to, as the correlation 
key could be composed of elements in different WSDLs (i.e. WSDL "A" operation 
initializes key, WSDL "B" operation correlates against key)

I would suggest automatically creating a new WSDL in the project called 
something like ProjectExtensibilityElements.wsdl and adding the Alias details 
there (automatically importing the required WSDLs). This could also be used for 
PLs (see issue 85417) 
Comment 2 Michael Frisino 2006-09-21 10:40:16 UTC
yes, there is already plan to do wrapper wsdl but the full details are not yet
finalized so please keep ideas coming for improving this story. 
Comment 3 mfoster 2006-09-22 21:34:12 UTC
Created attachment 34395 [details]
BPEL Aansluting Project
Comment 4 mfoster 2006-09-22 21:34:38 UTC
Created attachment 34396 [details]
CA Aansluiting Project
Comment 5 mfoster 2006-09-24 17:40:06 UTC
Created attachment 34424 [details]
BPEL Aansluting Project
Comment 6 mfoster 2006-09-24 17:40:35 UTC
Created attachment 34425 [details]
CA Aansluiting Project
Comment 7 Michael Frisino 2006-09-24 18:15:08 UTC
what is the difference between the copies of the projects attached here? there
seem to be two copies separated by two days? Can we ignore one copy?
Comment 8 Michael Frisino 2006-11-13 11:59:52 UTC
Marking this as duplicate of general wrapper wsdl feature issue. If there is
more reqeusted above basic wrapper wsdl, then we need to create a separate
Feature issue for those other features (i.e. special support for Property Alias,
for instance). But first check, there already may be other issue open for such
topic.

*** This issue has been marked as a duplicate of 88318 ***