[
https://issues.apache.org/jira/browse/SYNAPSE-856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13231919#comment-13231919
]
Dushan Sachinda Abeyruwan commented on SYNAPSE-856:
---------------------------------------------------
Hi,
I have enhanced the aggregate mediator, where aggregate message collector
expects Expressions for min and max values, and also I have modified the the
get-property where now we can share variable globally via AIXIS2 OPERATION
context, where now the following scenario works successfully
e.g
<property name="count" value="0" scope="operation"/>
<iterate xmlns:a="http://www.xxx.test.sample1.org"; preservePayload="true"
expression="expression">
<target soapAction="urn:getClients">
<sequence>
<filter source="$ctx:xxxx" regex="true">
<property name="count"
expression="get-property('operation','count')+1" scope="operation"/>
</filter>
</sequence>
</iterater>
<aggregate>
<completeCondition>
<messageCount xmlns:ns3="http://org.apache.synapse/xsd";
min="{get-property('operation','count')}" max="-1"/>
</completeCondition>
<onComplete xmlns:ns="http://org.apache.synapse/xsd";
xmlns:ns3="http://org.apache.synapse/xsd";
xmlns:m0="http://ws.xxx.org/dataservice"; expression="//m0:Clients">
<sequence key="getPoliciesForClientSeq"/>
</onComplete>
</aggregate
> Aggregate On complete message count to work with Expressions
> ------------------------------------------------------------
>
> Key: SYNAPSE-856
> URL: https://issues.apache.org/jira/browse/SYNAPSE-856
> Project: Synapse
> Issue Type: Improvement
> Components: Core
> Environment: Ubuntu 10.10 JDK 6
> Reporter: Dushan Sachinda Abeyruwan
> Attachments: synapse-core.patch
>
>
> Hi,
> Current aggregate component module is lacking of waiting minimum maximum
> messages before aggregate completes, now only static values are expected but
> when its comes to real world scenarios,we might have to proceed those Message
> count Min,Max to corporate with dynamic variables at run time, good examples
> is describes below,
> e.g:
> 1. Retrieving message as follows
> <users><user1><user2><user3><user4>........n<users>
> 2. Iterating each user, then depending on certain logic only few
> users will be allow to proceed other will be logged or. doing something else,
> 3. Then aggregater waits only the users who are success to get
> completed, in this sens the success count will be kept in property file where
> It SHOULD be able to share under different scopes
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
