[rules-users] What if Rules change frequently...

[jdepaul]

Edson Tirelli-3 wrote:
> ... you need to be aware that such activations will be created even if 
> it was already fired for the old rule...

Edson -  could you please expand your explanation a bit - would like to know
a little better what you meant above.

FYI - my goal is to assert each new Fact against the latest set of Rules
with minimum latency when rules change.  I would like to assert each
Event/Fact individually (not in an on-going conversation).  I want each
assertion to result in exactly ONE or ZERO matches to the current set of
rules in place and act on it only if Match occurs.

I envision having a component that holds Drools' RuleBase object as a
Singleton with current set of rules retrieved from the DataBase at
application initialization - the Singleton, would be used by multiple
threads in the ApplicationServer for each request.  Each thread would get a
RuleBase reference from the Singleton and create newWorkingMemory() EVERY
time, assert the Fact and FireAllRules and then be all done until the next
Event arrived...   By creating newWorkingMemory() every time for each Fact,
I'm hoping to achieve "isolation" of events - that is preventing multiple
rules being activated and firing.    When rules change, I'm hoping for some
mechanism (JBoss or custom) to update the RuleBase and its packages.  Is
this achievable using dynamic rules with JBoss?  

Please comment -

-- 
View this message in context: http://www.nabble.com/What-if-Rules-change-frequently...-tf3149726.html#a8737858
Sent from the drools - user mailing list archive at Nabble.com.