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: Issue 11 - noch ein mal - Proposal - CAM binding for BPEL


Having laid out a use case (see RTF below) - its time to next
consider how BPEL can support that use case (see link at bottom
of this email).

E.g. - using CAM as an external validation service for BPEL.
I'm picking this one as the simpler of the two use cases -
(once we have this figured out then we can do the harder
  assembly use case).

Looking at the requirements coming out of the Validation
use case - we have something like:

1) WSDL for CAM interface definition.
2) URL reference to CAM template involved, to be passed
    to the CAM processor to use for loading in the
    required validation rules.
3) Means to pass input XML content from BPEL to
    CAM external process so that CAM processor can
    accept it and process it according to the instruction in
    the CAM template from 2).  [could be via WSDL, or
    could be URL reference - two modes].
4) Context parameters - four optional ways of doing this
   i. URL reference to a CAM context instance (XML) / or
   ii. pass XML context instance directly via WSDL / or
   iii. just code context rules into CAM template itself from 2)
       [straight in the CAM header section area provided for this
   iv. Ignore - no context needed (not all actions require it).
5) Return - result codes - succeed / fail  and associated error
    structure to report back validation details on failed test(s)

My sense is that the binding comprises two chunks of stuff,
one is the WSDL, and then second is some XSD elements
and attributes that control the 2) thru 5) items, along with
corresponding <variables> on the BPEL side of the house
to pass content to and from.

Does this look like a good set of base requirements?

If not - what is missing / wrong?

If yes - can we make a first cut at some XML to
drive this with?

Thanks, DW.

----- Original Message ----- 
From: <jevdemon@microsoft.com>
To: <wsbpel-uc@lists.oasis-open.org>
Sent: Monday, March 15, 2004 8:12 PM
Subject: [wsbpel-uc] Groups - CAM-002.rtf uploaded

> The document CAM-002.rtf has been submitted by John Evdemon
(jevdemon@microsoft.com) to the WSBPEL Use Cases List document repository.
> Document Description:
> eBusiness Transaction binding with external service - Transaction
> An industry group needs to have a consistent way of documenting the
information exchanges for the scenarios its members are implementing.
Further more implementers need a consistent way of ensuring transaction
content is assembled according to the industry definitions of those
transactions. Each individual participant needs a consistent way of apply
context to their specific interchange transaction assembly.  The OASIS CAM
TC team has created a specification and toolset that can act as an external
service in this way. A WSDL definition of a CAM process can provide the
linkage between the CAM process and the BPEL. The BPEL will need to package
the XML content that requires assembly and pass that to the CAM process as
an XML structure. That structure may resemble the final transaction content
structure, but does not have to exactly match it. The CAM process will
assemble the information into the exact structure layout and details in XML
that are specifically required. CAM has an extensive set of functions that
permit manipulation of data strings and content formatting.  The CAM process
will return to the BPEL process the outcome from the external assembly
service, along with either a completed transaction document, or a delivery
result status.
> Download Document:
> View Document Details:
> PLEASE NOTE:  If the above links do not work for you, your email
> may be breaking the link into two pieces.  You may be able to copy and
> the entire link address into the address field of your web browser.
> To unsubscribe from this mailing list (and be removed from the roster of
the OASIS TC), go to

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