First of all, don't use automated time stamping of events; add a field carrying the (original) event time. I think you could also run the session in CLOUD mode.

Also, it may not be advisable to pull in facts and reason over them in the same rule. Perhaps retrieval and proper insertion of facts should even be coded in Java, kept separate from the rule logic.

Much depends on the required use cases for running those multiple sessions, and how canned events relate to other data.

-W


On 13 July 2011 02:13, rp2 <amanteja@gmail.com> wrote:

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