atom feed21 messages in org.oasis-open.lists.wsbpelRe: [wsbpel] Q: guidelines for reliab...
FromSent OnAttachments
LI Yanming / FTR&D / USSep 9, 2003 10:29 am 
Ron Ten-HoveSep 9, 2003 10:54 am 
Martin ChapmanSep 9, 2003 11:22 am 
Ugo CordaSep 9, 2003 11:23 am 
David RR Webber - XML ebusinessSep 9, 2003 11:24 am 
Ron Ten-HoveSep 9, 2003 11:43 am 
Ugo CordaSep 9, 2003 11:54 am 
Ron Ten-HoveSep 9, 2003 12:13 pm 
Ron Ten-HoveSep 9, 2003 12:16 pm 
David RR Webber - XML ebusinessSep 9, 2003 1:34 pm 
Ron Ten-HoveSep 9, 2003 3:51 pm 
David RR Webber - XML ebusinessSep 9, 2003 4:23 pm 
Eckenfels. BerndSep 10, 2003 6:49 am 
Ugo CordaSep 10, 2003 7:58 am 
Martin ChapmanSep 10, 2003 11:19 am 
David RR Webber - XML ebusinessSep 10, 2003 12:03 pm 
Ron Ten-HoveSep 10, 2003 12:31 pm 
Eckenfels. BerndSep 10, 2003 12:43 pm 
David RR Webber - XML ebusinessSep 10, 2003 7:45 pm 
Ron Ten-HoveSep 12, 2003 7:49 am 
David RR Webber - XML ebusinessSep 12, 2003 9:17 am 
Subject:Re: [wsbpel] Q: guidelines for reliability?
From:David RR Webber - XML ebusiness (Gnos@compuserve.com)
Date:Sep 9, 2003 1:34:35 pm
List:org.oasis-open.lists.wsbpel

Ron,

EXACTLY! This problem has already been solved by the CPA team!!

Why re-invent this? The partner role stuff in BPEL is weak compared to CPA - so makes sense to upgrade here.

Using your CPA you can point at the BPEL process and specify the QoS in the CPA. I've also very successfully templated this for CPA - so that the delivery options and combinations are simply drag-and-drop options within the CPA wizard UI.

Makes sense for us to liaise with the CPA team to ensure that a CPA can define BPEL processing adequately.

Looking at it they already have the means provided to point at a BPEL script. The BPEL engine may need to query the CPA to determine lowerlevel functionality - and that we may need to ensure there are the right "slots" for within the CPA schema.

Probably an excellent exercise to go thru anyway - to quantify the details that are relevant for BPEL.

Thanks, DW. ================================================================== Message text written by Ron Ten-Hove

These could be used by the deployer when selecting or creating the appropriate bindings for the abstract operation "acceptPayment".

This still wouldn't help the interoperability problem -- two deployers for two different engines that must interoperate must "exchange notes" to assure compatible bindings are chosen. This starts to become a very CPA-like exercise.

-Ron <