Dear
Mark,
As you
say this is an example and it is a fragment taken from an 'imaginary' BPEL
instance document. Thus it is not being proposed that the revised BPEL4WS
schema reference WS-C. The type attribute is actually of type 'QName' so
currently instance documents can reference any context message the designer
likes. So if you would like to write instead something
like:
<variable name=”receivedContext” type=”myown:ContextMessage” />
you
can do. So you have your wish already. The accompanying text
probably should counsel caution, apply some constraints, etc, but the schema
currently does not.
The
downside to this great flexibility is obviously potential lack of
interoperability, or only tiny islands of interoperability, if everyone does do
it their own way. Some care and some agreements will be required to use
the flexibility constructively without floundering in the
marsh.
Best
Regards,
Tony
|
Tony
Fletcher
Technical
Advisor
Choreology
Ltd. 68, Lombard Street, London EC3V 9L J
UK |
Phone:
|
+44
(0) 870 7390076 |
Mobile:
|
+44
(0) 7801 948219 |
Fax:
|
+44
(0) 870 7390077 |
Web: |
www.choreology.com |
Cohesions™ |
Business
transaction management software for application
coordination |
Work: tony.fletcher@choreology.com
|
Home:
amfletcher@iee.org |
The example in the proposal uses a
wscoor:CoordinationContext. Since part of the reason for doing this is to try
to prevent re-engineering if there are changes to context definitions later,
wouldn't it make more sense to define a BPEL specific construct that can then
(hopefully) be mapped to a WS-C, WS-Context or WS-whatever structure
later?
Mark.
----- Original Message -----
Sent: Wednesday, August 27, 2003 12:00
AM
Subject: [wsbpel] Issue - 54 -
Construct to hold Business transaction contexts
This issue has been added to the wsbpel issue list. The issues list is
posted as a Technical Committee document to the OASIS WSBPEL TC
pages on a regular basis. The current edition, as a TC document, is the
most recent document with the title in the "Issues" folder of the WSBPEL
TC document list - the next posting will include this issue. The list
editor's working copy, which will normally include an issue when it is
announced, is available at this
constant URL.
Issue - 54 - Construct to hold Business transaction contexts
Status: open Date added: 26 Aug 2003 Origin:
Choreology
submission on business transaction management (document
details), issue B Submitter: Peter Furniss Date
submitted: 26 August 2003 Description: A mechanism is needed
to hold business transaction contexts and participant identifications.
Changes: 26 Aug 2003 - new issue
To comment on this issue, please follow-up to this announcement on the
wsbpel@lists.oasis-open.org list (replying to this message should
automatically send your message to that list), or ensure the subject line as
you send it starts "Issue - 54 - [anything]" or is a reply to such a
message.
To add a new issue, see the issues procedures document.
To unsubscribe from this list, go to
http://www.oasis-open.org/apps/org/workgroup/wsbpel. Note:unsubscribing will
result in your withdrawal from this OASIS Technical Committee.
|