Hi,
I have a sample drl file in which I have written multiple rules. For each different rules when get fired I have started different processes.
for eg:
Rule1
when: some condition
then:
drools.getWorkingMemory.startprocess("id1");
Rule2
when: some condition
then:
drools.getWorkingMemory.startprocess("id2");
But the problem is that only that rule flow process gets fired every time which I have added to builder last. Also it is clear that it goes inside the then clause of Rule2 suppose but then again it starts process with id1.
Any help on how to resolve this or why is it happening is welcom,
Thanks
Santosh Mukherjee
On Tue, Jul 13, 2010 at 3:39 AM, nanic23
<nanic23@hotmail.com> wrote:
Hi cafebabe,
Thanks for your comment. I agree with you that work item ids are database
primary keys but in this simple (very simple) case I just decided to
harcoded as I know for a fact that the work item id is 1 because that is the
only work item and each time I run the test the tables are dropped and
recreated. So, there is never more than one row in the workItemInfo table
and the only row always has 1 as its id.
I could have stored the work item id or a work item object as a variable
(like you mentioned) but in this case wouldn't make a difference for the
timers.
Are timers working for you when you use persistence? I do complete work
items by workItem.getId() in all my code (other than this simple example
:)). My problem is NOT completing the work item, my problem is triggering
timers when persistence is enabled. The timers don't even trigger, thing
that should happen before even trying to complete the work item.
Thanks,
Nick.
--
View this message in context: http://drools-java-rules-engine.46999.n3.nabble.com/Implementing-Timers-With-Drools-Persistence-Enabled-tp923142p961658.html