Re: [wsbpel] Issue - 54 - Construct to hold Business transaction contexts

["Mark Little" <mark.little@arjuna.com>]

> 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.

Yes, we've been there too. However, I believe it is a surmountable problem.
Without trying to sound like a broken record, I'd recommend taking a look at
the WS-Context approach to this. Maybe we should take this off-line as well,
unless others think this is immediately important. (A similar discussion
came up in WS-Chor and we were asked to take it off-line as it wasn't in
"context" - no pun intended ;-)

>
> 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, I'm definitely going to take a look.

Mark.

>
> 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.<
>
>
> To unsubscribe from this mailing list (and be removed from the roster of
the OASIS TC), go to
http://www.oasis-open.org/apps/org/workgroup/wsbpel/members/leave_workgroup.
php.
>
>