Re: [wsbpel] Issue - 152 - Proposal to Vote

[Alex Yiu <alex.yiu@oracle.com>]

Option (B): Make the "reference-scheme" attribute of  of "service-ref" element optional:

The “bpws:service-ref” has an optional attribute called “reference-scheme” to to denote the URI of the reference interpretation scheme of service endpoint, which is the child element of bpws:service-ref.

Both the child element and optional "reference" URI constitutes the open content of "service-ref".
The semantics is just like other open-content model (e.g XML Schema).

The URI of reference scheme and the namespace URI of the child element of bpws:service-ref are not necessarily the same. Typically, this optional attribute is used ONLY when the child element of the “bpws:service-ref” is ambiguous by itself. The optional attribute supplies further information to disambiguate the usage of the content.

Example: different treatments of wsdl:service element

• If that attribute is not specified, use the namespace URI of the content element within the wrapper to determine the reference scheme of service endpoint.

• if the attribute is specified, use the URI as the reference scheme of service endpoint and treat the content element within the wrapper accordingly.
  • When the "reference-scheme" attribute is specified, the URI value is MOST LIKELY different from the namespace URI of the content element for EPR.
• When the BPEL container fails to interpret the combination of the "reference-scheme" attribute and the content element OR just the content element alone, a standard fault "bpws:UnsupportedReference" must be thrown.