RE: [rules-users] Decision table not triggering
Outside of the WM. There are a number of rules in this decision table, but
they all look just like this one. The way this works is that if it matches
any of these rules, then it's an approved request.
-----Original Message-----
From: rules-users-bounces(a)lists.jboss.org
[mailto:rules-users-bounces@lists.jboss.org] On Behalf Of Anstis, Michael
(M.)
Sent: Friday, August 08, 2008 3:54 AM
To: Rules Users List
Subject: RE: [rules-users] Decision table not triggering
I think you might need to post more of your source if possible.
Where are you setting PoolInfo.daysBeforeSummons to 5, outside WM and
before fireAllRules or within the RHS of another rule?
Thanks,
Mike
-----Original Message-----
From: rules-users-bounces(a)lists.jboss.org
[mailto:rules-users-bounces@lists.jboss.org] On Behalf Of Hehl, Thomas
Sent: 07 August 2008 21:41
To: 'Rules Users List'
Subject: RE: [rules-users] Decision table not triggering
Nope. Only one of each.
-----Original Message-----
From: rules-users-bounces(a)lists.jboss.org
[mailto:rules-users-bounces@lists.jboss.org] On Behalf Of Greg Barton
Sent: Thursday, August 07, 2008 4:33 PM
To: Rules Users List
Subject: Re: [rules-users] Decision table not triggering
Is there more than one PoolInfo object in working
memory? If so does any one of them match the rule?
Also, the rule conditions would create a cartesian
join because the PoolInfo and PostponementRequest are
not logically related. In other words, if you had
PoolInfo1, PoolInfo2, PostponementRequest1,
PostponementRequest2 in working memory, and all
matched the rule, you'd get the following rule
firings:
PoolInfo1, PostponementRequest1
PoolInfo1, PostponementRequest2
PoolInfo2, PostponementRequest1
PoolInfo2, PostponementRequest2
Probably not what you want.
GreG
--- "Hehl, Thomas" <Thomas.Hehl(a)acs-inc.com> wrote:
I have a unit test that calls a decision table that
generated the following
rule with drools 4.0.7:
#From row number: 10
rule "postponePart_10"
when
PoolInfo(courtLocation == "101",
daysBeforeSummons >= 7,
daysBeforeSummons <= 999)
postponementRequest:
PostponementRequest(requestDaysAfterSummons
>= 30, requestDaysAfterSummons <= 90,
requestedDayOfWeek >= 2,
requestedDayOfWeek <= 2)
then
postponementRequest.setAllowed(true);
end
This rule passes when daysBeforeSummons = 30. I
then change the
daysBeforeSummons to 5 and the rule still passes. I
have debugged this and
watched it run rule 10, so I don't know what else to
do. Does this look like
a bug?
Thom Hehl
Sr. eJuror Architect
ACS: Government Solutions
* Office (859) 277-8800 x 144
* Thomas.Hehl(a)acs-inc.com
<mailto:Thomas.Hehl@acs-inc.com>
1733 Harrodsburg Road
Lexington, KY 40504-3617
This e-mail message, including any attachments, is
for the sole use of the
intended recipient(s) and may contain confidential
and privileged
information. Any unauthorized review, use,
disclosure or distribution is
prohibited. If you are not the intended recipient,
please contact the sender
by reply e-mail and destroy all copies of the
original message and notify
sender via e-mail at Thomas.Hehl(a)acs-inc.com
<mailto:Thomas.Hehl@acs-inc.com> or by telephone at
859-277-8800 ext. 144.
Thank you.
> _______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users