OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

wsbpel message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Issue - 87 - Proposal for Vote - Part 1

The original proposal for vote contained two parts, one that defined the 
generic mechanism and another that specified language for specific 
bindings. In order to allow us to make forward progress I am removing 
the section on specific bindings for this vote and instead just focusing 
on the mechanism. This vote will not close issue 87 as, if it is passed, 
we will still need to decide if we wish to address any binding specific 

14.9 Application Data

Application data is data transmitted in a message outside
of the normal message channel, specifically data in a message that is
not bound to a WSDL message part referenced in the portType/operation
definition that applies to the sent or received message.

To enable BPEL processes to access application data the from-spec is
extended to include:

<from appDataForMessage="ncname"/>

The value of the appDataForMessage attribute MUST be the name of a WSDL
message type variable. The output of this from-spec will always follow
the schema:

<element name="applicationData" type="bpws:tApplicationData">

<complexType name="tApplicationData">
        <any processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
     <anyAttribute processContents="lax"/>

The application data will be recorded inside of the applicationData XML

To enable BPEL processes to set application data the to-spec is extended
to include:

<to appDataForMessage="ncname"/>

The schema of the data assigned using this to-spec MUST follow the
previously defined schema or a bpws:mismatchedAssignmentFailure MUST be

When a message is received by the BPEL process any application data
associated with the message MUST be made available via the application
data from-spec. The exact means by which application data is retrieved
from a message is binding specific and the binding definition has final
say as to what data will appear as application data but in general any
parts of the incoming message that do not have bindings to specific WSDL
message parts are considered application data. Similarly when a message
is sent if any application data has been associated with the message
then the application data MUST be sent with the outgoing message using
the rules defined for the particular binding in use.

Any application data associated with a WSDL message type variable is
replaced with application data from the incoming message, if any,
whenever that variable is used to receive a new message.

Schema Changes:

Add to tFrom:

<attribute name="appDataForMessage" type="NCName"/>

Add to to:

<attribute name="appDataForMessage" type="NCName"/>

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]