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: Re: [wsbpel] Issue - 54 - Construct to hold Business transaction contexts


Mark,

This stuff gets potentially ugly in a hurry!    I started out with this all
over in the OASIS CAM TC back six+ months ago.

We designed a context passing area there - and of course the
biggest potential "gotcha" is defining the semantics of the
parameters in that area - so that they can be locally interpreted
correctly - without requiring a sophisticated parser.  You quickly
run past schema datatype capabilites BTW - so that obvious
first-guess only gets you to the first step.   And then this ties
into the CPA and messaging too.

Anyway - this work is continuing between the BCM and CAM TCs
and you can view the details of the CAM approach in the CAM spec'
(its toward the back, right before the Addendum stuff).

Thanks, DW.

Message text written by "Mark Little"
> 
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.<



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