[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Issue - 111 - Proposal For Vote
111 - Extension Activities Proposal: Add an extensionActivityWrapper element to hold extension activities Introduce Section 11.9 New activities can be introduced for use in BPEL by placing them inside of the extensionActivityWrapper element. The contents of an extensionActivityWrapper element MUST be a single element that MUST make available BPEL's standard-attributes and standard-elements. If the element contained within the extensionActivityWrapper element is not recognized by the BPEL processor and is not subject to a mustUnderstand="true" requirement from an extension declaration then the unknown activity MUST be treated as if it were an empty activity. In all cases however any standard-attributes or standard-elements used on the contained activity MUST be treated as defined by this specification. <extensionActivityWrapper > <???? standard-attributes> standard-elements </????> </extensionActivityWrapper> Schema: Add to activity group: <element name="extensionActivityWrapper" type="bpws:textensionActivityWrapper"/> Add the following definition: <complexType name="textensionActivityWrapper"> <sequence> <any processContents="lax"/> </sequence> </complexType>
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]