I was just referring to facts that we're being placed into your
statefulknowledgesession. As I mentioned, I use a mechanism with an EJB to
manage my JPA entities before injecting them into the session. I passed on
a blog entry with a ruleflow example as that looks to do a similar thing but
within
So, Do you mean that for serializing the state of a StatefulKnowledgeSession
we must include our rules into a ruleflow? How do you upgrade your
KnowledgeBase without loosing the WM state?
Please check this issues:
https://jira.jboss.org/jira/browse/JBRULES-1946
https://jira.jboss.org/jira/browse
I neglected to mention my reply is from the viewpoint of changing entities
through the program that interacts with drools; if you need to sense changes
from another source to entities/tables in a database Greg's suggestion seems
the easiest and least resource intensive. Pushed actions from the dat
It can depend on how you want to use working memory as well. If you are
working statelessly, you can load objects through some type of transactional
framework, insert them into memory (or the ones relevant to you at that
moment in time) let Drools evaluate the objects, make changes and then
serial
I am also looking similar feature. We can currently use AOP to send event to
stream. However, we have events with relevant duration for days and some
time weeks. If server were to restart for maintenance, how do we restore to
the same state?
Daniel Miller-9 wrote:
>
> So I hope that someone ou
king memory.
>
> If you use oracle there's a specific mechanism for this called "Database
Change Notification"
>
> --- On Fri, 11/6/09, Daniel Miller versatile.com> wrote:
>
> > From: Daniel Miller versatile.com>
> > Subject: [rules-users] Main
org.drools.event.WorkingMemoryEventListener would be the other option, now
using changes to the Working Memory as the trigger to update the Data Base.
If you intend using rules that modify WM contents, you may have to have this
in addition to a DB change notification mechanism.-W
On Fri, Nov 6, 20
