Making the rules more complicated in order to achieve control over sending
messages to some other application does not strike me as the best option.
As an alternative, processed facts could be collected on the interface
between
Drools and your application A.
-W
On 13 April 2014 05:26, mohanm <mohanm.eee(a)gmail.com> wrote:
Hi Laune,
Drools is integrated to an application A which is communicating to another
application B through webservice. Based on the facts in the working memory
we are going to do send an request to Application B to do some action
either
create,update or delete existing events. All the calls to the Application B
is synchronous. If we have more and more requests going to Application B
through synchronous calls, Application B is taking time to process those
requests. we need to limit these calls as low as possible, Any faults at
device can generate more than 100 events which in turn converted in to
facts
and inserted into working memory. For each facts, I don't want to create
100
requests to Application B. I need to send only one request to Application B
for all the facts together, So we are using collection to control this.
While using collection we were facing the problem as mentioned below.
Hope I made you understand
--
View this message in context:
http://drools.46999.n3.nabble.com/Problem-with-Collection-tp4029219p40292...
Sent from the Drools: User forum mailing list archive at
Nabble.com.
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users