[rules-users] Detecting what fact/event properties have changed.
Currently drools supports listening to events when objects are inserted, updated or retracted. I would like to get information about a what properties have changed when the object was updated. Is there a way to do that? -- View this message in context: http://drools.46999.n3.nabble.com/Detecting-what-fact-event-properties-have-changed-tp3267788p3267788.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
Re: [rules-users] Temporal reasoning with external persistence not working
Could someone please provide an answer? -- View this message in context: http://drools.46999.n3.nabble.com/Temporal-reasoning-with-external-persistence-not-working-tp3158399p3163063.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
Re: [rules-users] Temporal reasoning with external persistence not working
Thanks. Basically I am trying to retrieve (and store) events from an external store like in http://magazine.redhat.com/2008/07/11/jboss-drools-meets-hibernate/ expect that the backing store in not a relational db but a custom key-value store. This example also does not show the facts/events being inserted. Is this incorrect? All it does is ... ... workingMemory.setGlobal(hibernateSession, session); // sets a hibernate session workingMemory.fireAllRules(); -- View this message in context: http://drools.46999.n3.nabble.com/Temporal-reasoning-with-external-persistence-not-working-tp3158399p3163303.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
Re: [rules-users] Temporal reasoning with external persistence not working
Wolfgang Laun-2 wrote: The example does not use events, as in @role(event). You can maintain a value of type java.util.Date in your hibernated facts, but don't make them events the way you do. It is important for me to use temporal reasoning and CEP, and hence HAD to define these as @events. In addition I wanted to load and persist these events from/in a custom non JPA compliant key-value store because I will be running multiple instances of drools as opposed to only one server. Therefore relying on RAM based working memory is not enough. What would be your suggestion in that regard? -- View this message in context: http://drools.46999.n3.nabble.com/Temporal-reasoning-with-external-persistence-not-working-tp3158399p3164267.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