OASIS Open Mailing List Archives  ·  All Lists  ·  dss-x  ·  2008-04

dss-x — archive

[Date Prev]  |  [Thread Prev]  |  [Thread Next]  |  [Date Next]   —  [Date Index]  |  [Thread Index]  |  [Month Index]  |  [List Home]

RE: Minor issue on te ebXML profile


Hello Andreas, To exchange ebXML messages using the profile, a DSS client and a DSS server could use an ebMS message service handler configured using a CPA like the one included in the appendix. That CPA could have been created (apart obviously from being hand-edited) by: - Merging a CPP for the client with a CPP for the server. - Transforming a CPA "template" using variable information for partner-specific parameters like Endpoint and PartyId. The first approach (CPP intersection) is the method discussed in the CPPA standard. However, the second approach (templates plus variables) seems to be the method that is more commonly used in ebXML projects (at least in my experience). This method is also supported by some ebXML products. (The CPPA TC is currently working on formalizing this approach, see http://www.oasis-open.org/apps/org/workgroup/ebxml-cppa/document.php?documen t_id=27623). Instead of a single sample CPA, I could have provided two sample CPPs, but they would still be templates. An alternative would have been to add an ebBP business process to document the message choreography. Perhaps in a future revision, if there is strong interest. BTW, the CPA and all other appendices are only an informative part of the profile. Kind regards, Pim

[Date Prev]  |  [Thread Prev]  |  [Thread Next]  |  [Date Next]   —  [Date Index]  |  [Thread Index]  |  [Month Index]  |  [List Home]