e.ode-bpel-schemas.1.3.6.source-code.wsbpel_main-draft-Sep-06-2005.xsd Maven / Gradle / Ivy
BPEL4WS Schema
2004-03-24: YIU-OSS: Alex Yiu: Extracted from wsbpel-specification-draft.doc (Rev 1.22 - Modified on 24 March, 2004)
2004-03-24: YIU-OSS: Alex Yiu: Updated targetNamespace with "2004/03"
2004-03-24: YIU-OSS: Alex Yiu: fixed a number of syntax typos (e.g remove complexContent)
2004-06-26: YIU-OSS: Alex Yiu: Using XMLSpy to do a re-indent
2004-06-28: YIU-OSS: Alex Yiu: Applying Issue 94 resolution by merging tActivityContainer and tActivityOrCompensateContainer
2004-06-28: YIU-OSS: Alex Yiu: Applying Issue 75 resolution: by allowing partnerLinks declaration within a scope
2004-06-28: YIU-OSS: Alex Yiu: Applying Issue 37 resolution: "initiate" attribute becomes a tri-value switch instead of a boolean switch
2004-07-19: YIU-OSS: Alex Yiu: Adding "service-ref" element and its definition for issue 34
2004-07-21: YIU-OSS: Alex Yiu: Applying Issue 43 and 44
2004-09-01: YIU-OSS: Alex Yiu: Applying Issue 146: Making tVariable Extensible
2004-09-01: YIU-OSS: Alex Yiu: Applying Issue 149: Adding formal documentation support to BPEL
2004-09-01: YIU-OSS: Alex Yiu: A bunch of misc cleanup for Issue 13
2004-10-20: YIU-OSS: Alex Yiu: Fixing schema problems discovered by Dieter Koenig
2004-10-20: YIU-OSS: Alex Yiu: Applying Issue 123
2004-10-20: YIU-OSS: Alex Yiu: Applying some non-normative changes suggested by Paul Brown
2004-11-30: YIU-OSS: Alex Yiu: Applying Issue 152 and 165
2004-12-02: YIU-OSS: Alex Yiu: Applying Issue 135 (TerminationHandler changes from Satish)
2005-04-02: curbera-oss: Paco Curbera: Applying Issue 93
2005-04-24: curbera-oss: Paco Curbera: Applying Issue 112
2005-05-01: YIU-OSS: Alex Yiu: Fixing XSD syntax typo for Issue 112
2005-05-02: YIU-OSS: Alex Yiu: Reapplying XSD syntax changes lost during CVS Migration:
(a) Moving terminationHandler from process level to scope level
(b) removing compensationHandler from the process level
(c) renaming an attribute of "scope" from "variableAccessSerializable" to "isolated"
(d) removing "enableInstanceCompensation" attribute from XSD
(e) removing "partner" and "partners" element
2005-05-06: Rev 1.18: Assaf Arkin: Applying Issue 160, added validate activity, validate attribute to assign, simple type tNCNames
2005-06-24: Rev 1.19: YIU-OSS: Alex Yiu: fixing minor typo in the Rev 1.18
2005-06-28: Rev 1.20: YIU-OSS: Alex Yiu: applying Issue 140 - adding "repeatUntil" activity
2005-07-25: Rev 1.21: YIU-OSS: Alex Yiu: Applying Issue 103, 199, 203 and Issue 196
2005-08-14: Rev 1.22: curbera-oss: Paco Curbera: Applying Issue 139.1, 147
2005-08-20: Rev 1.23: assaf-oss: Assaf Arkin: fixed issues 202, 206, 209, 214 and 132. (this comment is added by alex)
2005-08-29: Rev 1.24: YIU-OSS: Alex Yiu: rectify the definition of "forEach" (issue 147) according to the issue 204 by adding "scope" (note: we still need to apply the rest of issue 204.
2005-08-30: Rev 1.25: YIU-OSS: Alex Yiu:
Apply XSD changes for Issue 190, Issue 136, Issue 213.
Apply XSD Changes for Issue 111 and 11.1
Apply XSD Changes for Issue 192 by merging wsbpel_msgprop.xsd into this wsbpel_main.xsd
XSD Changes in Issue 145 was missing. Re-apply it here.
This type is extended by other component types
to allow elements and attributes from
other namespaces to be added.
Addtional constraint:
- rethrow activity can be used ONLY within a fault handler
(i.e. "catch" element of bpws:tCatch type and
"catchAll" element of bpws:tActivityOrCompensateContainer type )
- compensate activity can be used ONLY within a fault handler or a compensation handler
(i.e. bpws:tActivityOrCompensateContainer type)
An empty extension from bpws:tActivityContainer to denote where the compensate activity is allowed
This element can be used within a from-spec.
This type definition is for service reference container.
This container is used as envelope to wrap around the actual endpoint reference value,
when a BPEL process interacts the endpoint reference of a partnerLink.
It provides pluggability of different versions of service referencing schemes
being used within a BPEL program. The design pattern here is similar to those of
expression language.
© 2015 - 2025 Weber Informatics LLC | Privacy Policy