NEW ISSUE: Include mapping of interface.partnerLinkType to interface.wsdl

[Anish Karmarkar <Anish.Karmarkar@oracle.com>]

Title: Include mapping of interface.partnerLinkType to interface.wsdl

Target: BPEL C&I

Description:
The BPEL C&I spec defines a new interface type called 
interface.partnerLinkType in section 2.3. That section also says: "This 
form does not provide any more information than is present in the 
<interface.wsdl> element."

It is quite possible that services and references of a component that 
uses implementation.bpel and interface.partnerLinkType may be wired to 
components that have interface.wsdl.

The BPEL C&I spec should specific how to generate an equivalent 
interface.wsdl from a interface.partnerLinkType.

Proposal:
Something along the lines of:

A partnerLinkType that has only one role:
The equivalent interface.wsdl will be a non-callback interface. The 
interface.wsdl's 'interface' attribute will point to the same portType 
as the one pointed to by 
plnk:partnerLinkType/plnk:role/plnk:portType/@name attribute.
Note that partnerLinkType points to the portType's QNames whereas 
interface.wsdl uses the URL of the form <target-NS>#wsdl.interface(...).

A partnerLinkType that has two roles:
The equivalent interface.wsdl will be a callback interface. The forward 
interface will have the same portType as the one pointed to by the 
partnerLinkType role whose @name attribute value matches that of the 
@serviceRole attribute. The callback interface be the portType that is 
not assigned to the forward interface.

-Anish
--