The facts should be immutable, so you should remove them and insert again when they change.
If your facts change often, you have to consider to use fusion where your facts will be events.
Hello,
I'm working on a project which uses Drools as a component. It is connected
to a web server. Every time a request arrives to web server, it in turn
loads the facts and invokes fireAllRules. Facts do change over time but
rules do not ... I'm bit concerned that this may not be correct of using
Drools, since we are constantly doing setup /tear down.
Keep facts in memory and updating them when necessary - that requires major
change in the architecture of the application.
I want to know - has anyone done something similar? Does it lead major
problems in future? Performance Issues?
Regards
Ejaz
--
View this message in context: http://drools.46999.n3.nabble.com/What-is-the-correct-approach-towards-using-Drools-tp4022291.html
Sent from the Drools: User forum mailing list archive at Nabble.com.
_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users