[
https://issues.apache.org/jira/browse/TUSCANY-1668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12526114
]
gengshaoguang commented on TUSCANY-1668:
----------------------------------------
Let me say some thing shortly:
To implement a component as a BPEL could be easiser, because to any client, a
BPEL is no more than a wsdl, so Tuscany could reference a BPEL just like a WS.
To orchestrate SCA component into BPEL could be easier if they are all WS
binded, BPEL could leverage any resource as WS.
Here is a key: wether we are going to make a BPEL engine SCA compatible, so
that it may leverage SCA component directly. And this will boost the
performance of a bpel if most of the "PartnetLink" are local.
> Tuscany User request for BPEL integration with Tuscany
> ------------------------------------------------------
>
> Key: TUSCANY-1668
> URL: https://issues.apache.org/jira/browse/TUSCANY-1668
> Project: Tuscany
> Issue Type: New Feature
> Components: Java SCA BPEL Implementation Extension
> Environment: General
> Reporter: haleh mahbod
> Assignee: Luciano Resende
> Fix For: Java-SCA-Next
>
>
> I am creating this JIRA based on email thread started by Jeff Anderson
> (Deloitte)
> http://www.mail-archive.com/[EMAIL PROTECTED]/msg01683.html
> Request:
> advanced orchestration/BPEL-the ability to create composites and references
> that can take advantage of the BPEL capability will become a requirement as
> our client starts to adopt our platform, which is based on Tuscany, across
> the enterprise. I understand that some integration work is going on with a
> BPEL container (can't remember the name) but the more that this work is
> extended to be a robust solution, and the more likely it is that our plan
> will adopt this BPEL container gardening going for another vendor backed
> product.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
