You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@airavata.apache.org by "Patanachai Tangchaisin (JIRA)" <ji...@apache.org> on 2011/07/27 19:30:10 UTC
[jira] [Commented] (AIRAVATA-13) Add For-Each Capabilities to the
XBaya Dynamic Execution
[ https://issues.apache.org/jira/browse/AIRAVATA-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13071874#comment-13071874 ]
Patanachai Tangchaisin commented on AIRAVATA-13:
------------------------------------------------
I attach the patch to enable for-each capability to XBaya. The patch can be applied to airavata/trunk.
But, this is a primitive function for for-each i.e. inside For-EndFor component there can be only one Web Service Node.
> Add For-Each Capabilities to the XBaya Dynamic Execution
> ---------------------------------------------------------
>
> Key: AIRAVATA-13
> URL: https://issues.apache.org/jira/browse/AIRAVATA-13
> Project: Airavata
> Issue Type: New Feature
> Components: XBaya
> Reporter: Suresh Marru
> Attachments: iteration.pdf, patch.txt
>
>
> For data parallel applications, often an array of data has to be processed. BPEL specifications defines this as a For-Each capability where a Service A will output an array (it can be anything of the supported types) and Service B outputs any output type. Service C has to be looped through for each of the array element outputted by Service A. Once all the instances complete, the output is made into a array and passed onto Service D. This capability is described in BPEL specification and described in [1]
> [1] - http://www-01.ibm.com/support/docview.wss?uid=swg27011753
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira