11:11 a.m.
All,
I'm having a problem using memberOf combined with a collect statement. My
test includes 3 rules each written to output the same results (I think), but
I get different results (depending on which version of Drools I use).
The rules are:
rule "TestMemberOf"
salience 10
when
$messages: ArrayList() from collect (Message(status == 100))
$wrappers: ArrayList() from collect (Wrapper(message memberOf
$messages))
then
System.out.println("TestMemberOf: " + $wrappers.size());
end
rule "TestEval1"
salience 9
when
$messages: ArrayList() from collect (Message(status == 100))
$wrappers: ArrayList() from collect (Wrapper($message: message,
eval($messages.contains($message))))
then
System.out.println("TestEval1: " + $wrappers.size());
end
rule "TestEval2"
salience 8
when
$wrappers: ArrayList() from collect (Wrapper($message: message,
eval($message.getStatus() == 100)))
then
System.out.println("TestEval2: " + $wrappers.size());
end
The output is (by version):
4.0.0
TestMemberOf: 0
TestEval1: 0
TestEval2: 2
4.0.1
TestMemberOf: 0
TestEval1: 2
TestEval2: 2
4.0.2.SNAPSHOT (taken 9/18/07)
TestMemberOf: 0
TestEval1: 2
TestEval2: 2
The correct output should be:
TestMemberOf: 2
TestEval1: 2
TestEval2: 2
Am I using memberOf correctly? Is there some issue using an eval to test
conditions on a list created by a collect?
Any help would be appreciated.
Attached is the full example.
Thanks,
-Chris West
12:02 p.m.
Chris,
Thanks for reporting this.
I fixed a bug in 4.0.0 (released in 4.0.1) that causes you to see the
correct value for "TestEval1" in 4.0.1 and later versions. Although, at that
time I missed the memberOf scenario. I know why it happens (shadow fact
related), but now I need to figure out a way to fix it.
May I ask you to open a ticket for that?
Thanks,
Edson
2007/9/18, Chris West <crayzfishr(a)gmail.com>:
All,
I'm having a problem using memberOf combined with a collect statement. My
test includes 3 rules each written to output the same results (I think), but
I get different results (depending on which version of Drools I use).
The rules are:
rule "TestMemberOf"
salience 10
when
$messages: ArrayList() from collect (Message(status == 100))
$wrappers: ArrayList() from collect (Wrapper(message memberOf
$messages))
then
System.out.println("TestMemberOf: " + $wrappers.size());
end
rule "TestEval1"
salience 9
when
$messages: ArrayList() from collect (Message(status == 100))
$wrappers: ArrayList() from collect (Wrapper($message: message,
eval($messages.contains($message))))
then
System.out.println("TestEval1: " + $wrappers.size());
end
rule "TestEval2"
salience 8
when
$wrappers: ArrayList() from collect (Wrapper($message: message,
eval($message.getStatus() == 100)))
then
System.out.println("TestEval2: " + $wrappers.size());
end
The output is (by version):
4.0.0
TestMemberOf: 0
TestEval1: 0
TestEval2: 2
4.0.1
TestMemberOf: 0
TestEval1: 2
TestEval2: 2
4.0.2.SNAPSHOT (taken 9/18/07)
TestMemberOf: 0
TestEval1: 2
TestEval2: 2
The correct output should be:
TestMemberOf: 2
TestEval1: 2
TestEval2: 2
Am I using memberOf correctly? Is there some issue using an eval to test
conditions on a list created by a collect?
Any help would be appreciated.
Attached is the full example.
Thanks,
-Chris West
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
--
Edson Tirelli
Software Engineer - JBoss Rules Core Developer
Office: +55 11 3529-6000
Mobile: +55 11 9287-5646
JBoss, a division of Red Hat @ www.jboss.com
2:21 p.m.
http://jira.jboss.com/jira/browse/JBRULES-1204
On 9/18/07, Edson Tirelli <tirelli(a)post.com> wrote:
Chris,
Thanks for reporting this.
I fixed a bug in 4.0.0 (released in 4.0.1) that causes you to see the
correct value for "TestEval1" in 4.0.1 and later versions. Although, at
that time I missed the memberOf scenario. I know why it happens (shadow fact
related), but now I need to figure out a way to fix it.
May I ask you to open a ticket for that?
Thanks,
Edson
2007/9/18, Chris West <crayzfishr(a)gmail.com>:
>
> All,
>
> I'm having a problem using memberOf combined with a collect statement.
> My test includes 3 rules each written to output the same results (I think),
> but I get different results (depending on which version of Drools I use).
>
> The rules are:
>
>
> rule "TestMemberOf"
> salience 10
> when
> $messages: ArrayList() from collect (Message(status == 100))
> $wrappers: ArrayList() from collect (Wrapper(message memberOf
> $messages))
> then
> System.out.println("TestMemberOf: " + $wrappers.size());
> end
>
> rule "TestEval1"
> salience 9
> when
> $messages: ArrayList() from collect (Message(status == 100))
> $wrappers: ArrayList() from collect (Wrapper($message: message,
> eval($messages.contains($message))))
> then
> System.out.println("TestEval1: " + $wrappers.size());
> end
>
> rule "TestEval2"
> salience 8
> when
> $wrappers: ArrayList() from collect (Wrapper($message: message,
> eval($message.getStatus() == 100)))
> then
> System.out.println("TestEval2: " + $wrappers.size());
> end
>
>
>
> The output is (by version):
>
> 4.0.0
>
> TestMemberOf: 0
> TestEval1: 0
> TestEval2: 2
>
> 4.0.1
>
> TestMemberOf: 0
> TestEval1: 2
> TestEval2: 2
>
> 4.0.2.SNAPSHOT (taken 9/18/07)
>
> TestMemberOf: 0
> TestEval1: 2
> TestEval2: 2
>
>
> The correct output should be:
>
> TestMemberOf: 2
> TestEval1: 2
> TestEval2: 2
>
>
> Am I using memberOf correctly? Is there some issue using an eval to
> test conditions on a list created by a collect?
>
> Any help would be appreciated.
>
> Attached is the full example.
>
> Thanks,
> -Chris West
>
>
>
> _______________________________________________
> rules-users mailing list
> rules-users(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/rules-users
>
>
>
--
Edson Tirelli
Software Engineer - JBoss Rules Core Developer
Office: +55 11 3529-6000
Mobile: +55 11 9287-5646
JBoss, a division of Red Hat @ www.jboss.com
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
2:29 p.m.
Edson,
So now my dilemma is that I cannot use 4.0.0 due to JBRULES-1204, but I
cannot use 4.0.1 or 4.0.2-SNAPSHOT due to JBRULES-1203. Below is an actual
block from my rule. I'd like to transform it into something like
"TestEval2" from my example, but it is more complicated. Can it be
rewritten like "TestEval2"?
$sorties: ArrayList() from collect (AirPlanSortie(event ==
$currentEvent, spare == false, superSpare == false))
$statuses: ArrayList($sortieSize: size) from collect
(SortieStatus(state != SortieState.CANCELLED, $sortie1: sortie, eval
($sorties.contains($sortie1))))
$launches: ArrayList(size > 0, size == $sortieSize) from collect
(LaunchAircraftStatus(launched == true, $sortie0: sortie,
eval($sortie0.getEvent().equals($currentEvent))))
-Chris
On 9/18/07, Edson Tirelli <tirelli(a)post.com> wrote:
Chris,
Thanks for reporting this.
I fixed a bug in 4.0.0 (released in 4.0.1) that causes you to see the
correct value for "TestEval1" in 4.0.1 and later versions. Although, at
that time I missed the memberOf scenario. I know why it happens (shadow fact
related), but now I need to figure out a way to fix it.
May I ask you to open a ticket for that?
Thanks,
Edson
2007/9/18, Chris West <crayzfishr(a)gmail.com>:
>
> All,
>
> I'm having a problem using memberOf combined with a collect statement.
> My test includes 3 rules each written to output the same results (I think),
> but I get different results (depending on which version of Drools I use).
>
> The rules are:
>
>
> rule "TestMemberOf"
> salience 10
> when
> $messages: ArrayList() from collect (Message(status == 100))
> $wrappers: ArrayList() from collect (Wrapper(message memberOf
> $messages))
> then
> System.out.println("TestMemberOf: " + $wrappers.size());
> end
>
> rule "TestEval1"
> salience 9
> when
> $messages: ArrayList() from collect (Message(status == 100))
> $wrappers: ArrayList() from collect (Wrapper($message: message,
> eval($messages.contains($message))))
> then
> System.out.println("TestEval1: " + $wrappers.size());
> end
>
> rule "TestEval2"
> salience 8
> when
> $wrappers: ArrayList() from collect (Wrapper($message: message,
> eval($message.getStatus() == 100)))
> then
> System.out.println("TestEval2: " + $wrappers.size());
> end
>
>
>
> The output is (by version):
>
> 4.0.0
>
> TestMemberOf: 0
> TestEval1: 0
> TestEval2: 2
>
> 4.0.1
>
> TestMemberOf: 0
> TestEval1: 2
> TestEval2: 2
>
> 4.0.2.SNAPSHOT (taken 9/18/07)
>
> TestMemberOf: 0
> TestEval1: 2
> TestEval2: 2
>
>
> The correct output should be:
>
> TestMemberOf: 2
> TestEval1: 2
> TestEval2: 2
>
>
> Am I using memberOf correctly? Is there some issue using an eval to
> test conditions on a list created by a collect?
>
> Any help would be appreciated.
>
> Attached is the full example.
>
> Thanks,
> -Chris West
>
>
>
> _______________________________________________
> rules-users mailing list
> rules-users(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/rules-users
>
>
>
--
Edson Tirelli
Software Engineer - JBoss Rules Core Developer
Office: +55 11 3529-6000
Mobile: +55 11 9287-5646
JBoss, a division of Red Hat @ www.jboss.com
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
3:21 p.m.
Chris,
Do you really need to "collect" all these facts? Are you doing anything
with these lists? It would be easier if you can show me the full rule, but
seems to me that maybe you can avoid some or all of these collects. Remember
that collect is a heavy CE, so it is always good to avoid when possible.
Anyway, there should be no problem if you use eval(). The problem in
JBRULES-1204 only affects memberOf operator, since the fix I implemented in
http://jira.jboss.org/jira/browse/JBRULES-1115 fixed the eval()s.
I will fix 1204 asap.
[]s
Edson
2007/9/18, Chris West <crayzfishr(a)gmail.com>:
Edson,
So now my dilemma is that I cannot use 4.0.0 due to JBRULES-1204, but I
cannot use 4.0.1 or 4.0.2-SNAPSHOT due to JBRULES-1203. Below is an
actual block from my rule. I'd like to transform it into something like
"TestEval2" from my example, but it is more complicated. Can it be
rewritten like "TestEval2"?
$sorties: ArrayList() from collect (AirPlanSortie(event ==
$currentEvent, spare == false, superSpare == false))
$statuses: ArrayList($sortieSize: size) from collect
(SortieStatus(state != SortieState.CANCELLED, $sortie1: sortie, eval
($sorties.contains($sortie1))))
$launches: ArrayList(size > 0, size == $sortieSize) from collect
(LaunchAircraftStatus(launched == true, $sortie0: sortie,
eval($sortie0.getEvent().equals($currentEvent))))
-Chris
On 9/18/07, Edson Tirelli <tirelli(a)post.com> wrote:
>
>
> Chris,
>
> Thanks for reporting this.
>
> I fixed a bug in 4.0.0 (released in 4.0.1) that causes you to see
> the correct value for "TestEval1" in 4.0.1 and later versions. Although,
> at that time I missed the memberOf scenario. I know why it happens (shadow
> fact related), but now I need to figure out a way to fix it.
>
> May I ask you to open a ticket for that?
>
> Thanks,
> Edson
>
>
> 2007/9/18, Chris West < crayzfishr(a)gmail.com>:
> >
> > All,
> >
> > I'm having a problem using memberOf combined with a collect
> > statement. My test includes 3 rules each written to output the same results
> > (I think), but I get different results (depending on which version of Drools
> > I use).
> >
> > The rules are:
> >
> >
> > rule "TestMemberOf"
> > salience 10
> > when
> > $messages: ArrayList() from collect (Message(status == 100))
> > $wrappers: ArrayList() from collect (Wrapper(message memberOf
> > $messages))
> > then
> > System.out.println("TestMemberOf: " + $wrappers.size());
> > end
> >
> > rule "TestEval1"
> > salience 9
> > when
> > $messages: ArrayList() from collect (Message(status == 100))
> > $wrappers: ArrayList() from collect (Wrapper($message:
> > message, eval($messages.contains($message))))
> > then
> > System.out.println("TestEval1: " + $wrappers.size());
> > end
> >
> > rule "TestEval2"
> > salience 8
> > when
> > $wrappers: ArrayList() from collect (Wrapper($message:
> > message, eval($message.getStatus() == 100)))
> > then
> > System.out.println("TestEval2: " + $wrappers.size());
> > end
> >
> >
> >
> > The output is (by version):
> >
> > 4.0.0
> >
> > TestMemberOf: 0
> > TestEval1: 0
> > TestEval2: 2
> >
> > 4.0.1
> >
> > TestMemberOf: 0
> > TestEval1: 2
> > TestEval2: 2
> >
> > 4.0.2.SNAPSHOT (taken 9/18/07)
> >
> > TestMemberOf: 0
> > TestEval1: 2
> > TestEval2: 2
> >
> >
> > The correct output should be:
> >
> > TestMemberOf: 2
> > TestEval1: 2
> > TestEval2: 2
> >
> >
> > Am I using memberOf correctly? Is there some issue using an eval to
> > test conditions on a list created by a collect?
> >
> > Any help would be appreciated.
> >
> > Attached is the full example.
> >
> > Thanks,
> > -Chris West
> >
> >
> >
> > _______________________________________________
> > rules-users mailing list
> > rules-users(a)lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/rules-users
> >
> >
> >
>
>
> --
> Edson Tirelli
> Software Engineer - JBoss Rules Core Developer
> Office: +55 11 3529-6000
> Mobile: +55 11 9287-5646
> JBoss, a division of Red Hat @ www.jboss.com
> _______________________________________________
> 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
--
Edson Tirelli
Software Engineer - JBoss Rules Core Developer
Office: +55 11 3529-6000
Mobile: +55 11 9287-5646
JBoss, a division of Red Hat @ www.jboss.com
3:43 p.m.
The fix for 1115 and fix for 1204 you're working will not help me unless
1203 is fixed, because all versions of code after 4.0.0 are affected by
1203, and it is a showstopper for me since I use JDK dynamic proxies as
facts.
-Chris
On 9/18/07, Edson Tirelli <tirelli(a)post.com> wrote:
Chris,
Do you really need to "collect" all these facts? Are you doing
anything with these lists? It would be easier if you can show me the full
rule, but seems to me that maybe you can avoid some or all of these
collects. Remember that collect is a heavy CE, so it is always good to avoid
when possible.
Anyway, there should be no problem if you use eval(). The problem in
JBRULES-1204 only affects memberOf operator, since the fix I implemented in
http://jira.jboss.org/jira/browse/JBRULES-1115
fixed the eval()s.
I will fix 1204 asap.
[]s
Edson
2007/9/18, Chris West <crayzfishr(a)gmail.com>:
>
> Edson,
>
> So now my dilemma is that I cannot use 4.0.0 due to JBRULES-1204, but I
> cannot use 4.0.1 or 4.0.2-SNAPSHOT due to JBRULES-1203. Below is an
> actual block from my rule. I'd like to transform it into something like
> "TestEval2" from my example, but it is more complicated. Can it be
> rewritten like "TestEval2"?
>
> $sorties: ArrayList() from collect (AirPlanSortie(event ==
> $currentEvent, spare == false, superSpare == false))
>
> $statuses: ArrayList($sortieSize: size) from collect
> (SortieStatus(state != SortieState.CANCELLED, $sortie1: sortie, eval
> ($sorties.contains($sortie1))))
>
> $launches: ArrayList(size > 0, size == $sortieSize) from collect
> (LaunchAircraftStatus(launched == true, $sortie0: sortie,
> eval($sortie0.getEvent().equals($currentEvent))))
>
> -Chris
>
>
> On 9/18/07, Edson Tirelli < tirelli(a)post.com> wrote:
> >
> >
> > Chris,
> >
> > Thanks for reporting this.
> >
> > I fixed a bug in 4.0.0 (released in 4.0.1) that causes you to see
> > the correct value for "TestEval1" in 4.0.1 and later versions.
> > Although, at that time I missed the memberOf scenario. I know why it happens
> > (shadow fact related), but now I need to figure out a way to fix it.
> >
> > May I ask you to open a ticket for that?
> >
> > Thanks,
> > Edson
> >
> >
> > 2007/9/18, Chris West < crayzfishr(a)gmail.com>:
> > >
> > > All,
> > >
> > > I'm having a problem using memberOf combined with a collect
> > > statement. My test includes 3 rules each written to output the same
results
> > > (I think), but I get different results (depending on which version of
Drools
> > > I use).
> > >
> > > The rules are:
> > >
> > >
> > > rule "TestMemberOf"
> > > salience 10
> > > when
> > > $messages: ArrayList() from collect (Message(status == 100))
> > > $wrappers: ArrayList() from collect (Wrapper(message
> > > memberOf $messages))
> > > then
> > > System.out.println("TestMemberOf: " +
$wrappers.size());
> > > end
> > >
> > > rule "TestEval1"
> > > salience 9
> > > when
> > > $messages: ArrayList() from collect (Message(status == 100))
> > >
> > > $wrappers: ArrayList() from collect (Wrapper($message:
> > > message, eval($messages.contains($message))))
> > > then
> > > System.out.println("TestEval1: " + $wrappers.size());
> > > end
> > >
> > > rule "TestEval2"
> > > salience 8
> > > when
> > > $wrappers: ArrayList() from collect (Wrapper($message:
> > > message, eval($message.getStatus() == 100)))
> > > then
> > > System.out.println("TestEval2: " + $wrappers.size());
> > > end
> > >
> > >
> > >
> > > The output is (by version):
> > >
> > > 4.0.0
> > >
> > > TestMemberOf: 0
> > > TestEval1: 0
> > > TestEval2: 2
> > >
> > > 4.0.1
> > >
> > > TestMemberOf: 0
> > > TestEval1: 2
> > > TestEval2: 2
> > >
> > > 4.0.2.SNAPSHOT (taken 9/18/07)
> > >
> > > TestMemberOf: 0
> > > TestEval1: 2
> > > TestEval2: 2
> > >
> > >
> > > The correct output should be:
> > >
> > > TestMemberOf: 2
> > > TestEval1: 2
> > > TestEval2: 2
> > >
> > >
> > > Am I using memberOf correctly? Is there some issue using an eval to
> > > test conditions on a list created by a collect?
> > >
> > > Any help would be appreciated.
> > >
> > > Attached is the full example.
> > >
> > > Thanks,
> > > -Chris West
> > >
> > >
> > >
> > > _______________________________________________
> > > rules-users mailing list
> > > rules-users(a)lists.jboss.org
> > > https://lists.jboss.org/mailman/listinfo/rules-users
> > >
> > >
> > >
> >
> >
> > --
> > Edson Tirelli
> > Software Engineer - JBoss Rules Core Developer
> > Office: +55 11 3529-6000
> > Mobile: +55 11 9287-5646
> > JBoss, a division of Red Hat @ www.jboss.com
> > _______________________________________________
> > 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
>
>
--
Edson Tirelli
Software Engineer - JBoss Rules Core Developer
Office: +55 11 3529-6000
Mobile: +55 11 9287-5646
JBoss, a division of Red Hat @ www.jboss.com
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
4:12 p.m.
Chris,
Ok, 1203 is in the pipeline too...
[]s
Edson
2007/9/18, Chris West <crayzfishr(a)gmail.com>:
The fix for 1115 and fix for 1204 you're working will not help me unless
1203 is fixed, because all versions of code after 4.0.0 are affected by
1203, and it is a showstopper for me since I use JDK dynamic proxies as
facts.
-Chris
On 9/18/07, Edson Tirelli <tirelli(a)post.com> wrote:
>
>
> Chris,
>
> Do you really need to "collect" all these facts? Are you doing
> anything with these lists? It would be easier if you can show me the full
> rule, but seems to me that maybe you can avoid some or all of these
> collects. Remember that collect is a heavy CE, so it is always good to avoid
> when possible.
>
> Anyway, there should be no problem if you use eval(). The problem in
> JBRULES-1204 only affects memberOf operator, since the fix I implemented in
http://jira.jboss.org/jira/browse/JBRULES-1115
> fixed the eval()s.
>
> I will fix 1204 asap.
>
> []s
> Edson
>
>
> 2007/9/18, Chris West < crayzfishr(a)gmail.com>:
> >
> > Edson,
> >
> > So now my dilemma is that I cannot use 4.0.0 due to JBRULES-1204, but
> > I cannot use 4.0.1 or 4.0.2-SNAPSHOT due to JBRULES-1203. Below is an
> > actual block from my rule. I'd like to transform it into something like
> > "TestEval2" from my example, but it is more complicated. Can it be
> > rewritten like "TestEval2"?
> >
> > $sorties: ArrayList() from collect (AirPlanSortie(event ==
> > $currentEvent, spare == false, superSpare == false))
> >
> > $statuses: ArrayList($sortieSize: size) from collect
> > (SortieStatus(state != SortieState.CANCELLED, $sortie1: sortie, eval
> > ($sorties.contains($sortie1))))
> >
> > $launches: ArrayList(size > 0, size == $sortieSize) from
> > collect (LaunchAircraftStatus(launched == true, $sortie0: sortie,
> > eval($sortie0.getEvent().equals($currentEvent))))
> >
> > -Chris
> >
> >
> > On 9/18/07, Edson Tirelli < tirelli(a)post.com> wrote:
> > >
> > >
> > > Chris,
> > >
> > > Thanks for reporting this.
> > >
> > > I fixed a bug in 4.0.0 (released in 4.0.1) that causes you to
> > > see the correct value for "TestEval1" in 4.0.1 and later
versions.
> > > Although, at that time I missed the memberOf scenario. I know why it
happens
> > > (shadow fact related), but now I need to figure out a way to fix it.
> > >
> > > May I ask you to open a ticket for that?
> > >
> > > Thanks,
> > > Edson
> > >
> > >
> > > 2007/9/18, Chris West < crayzfishr(a)gmail.com>:
> > > >
> > > > All,
> > > >
> > > > I'm having a problem using memberOf combined with a collect
> > > > statement. My test includes 3 rules each written to output the same
results
> > > > (I think), but I get different results (depending on which version of
Drools
> > > > I use).
> > > >
> > > > The rules are:
> > > >
> > > >
> > > > rule "TestMemberOf"
> > > > salience 10
> > > > when
> > > > $messages: ArrayList() from collect (Message(status ==
> > > > 100))
> > > > $wrappers: ArrayList() from collect (Wrapper(message
> > > > memberOf $messages))
> > > > then
> > > > System.out.println("TestMemberOf: " +
$wrappers.size());
> > > > end
> > > >
> > > > rule "TestEval1"
> > > > salience 9
> > > > when
> > > > $messages: ArrayList() from collect (Message(status ==
> > > > 100))
> > > > $wrappers: ArrayList() from collect (Wrapper($message:
> > > > message, eval($messages.contains($message))))
> > > > then
> > > > System.out.println("TestEval1: " +
$wrappers.size());
> > > > end
> > > >
> > > > rule "TestEval2"
> > > > salience 8
> > > > when
> > > > $wrappers: ArrayList() from collect (Wrapper($message:
> > > > message, eval($message.getStatus() == 100)))
> > > > then
> > > > System.out.println("TestEval2: " +
$wrappers.size());
> > > > end
> > > >
> > > >
> > > >
> > > > The output is (by version):
> > > >
> > > > 4.0.0
> > > >
> > > > TestMemberOf: 0
> > > > TestEval1: 0
> > > > TestEval2: 2
> > > >
> > > > 4.0.1
> > > >
> > > > TestMemberOf: 0
> > > > TestEval1: 2
> > > > TestEval2: 2
> > > >
> > > > 4.0.2.SNAPSHOT (taken 9/18/07)
> > > >
> > > > TestMemberOf: 0
> > > > TestEval1: 2
> > > > TestEval2: 2
> > > >
> > > >
> > > > The correct output should be:
> > > >
> > > > TestMemberOf: 2
> > > > TestEval1: 2
> > > > TestEval2: 2
> > > >
> > > >
> > > > Am I using memberOf correctly? Is there some issue using an eval
> > > > to test conditions on a list created by a collect?
> > > >
> > > > Any help would be appreciated.
> > > >
> > > > Attached is the full example.
> > > >
> > > > Thanks,
> > > > -Chris West
> > > >
> > > >
> > > >
> > > > _______________________________________________
> > > > rules-users mailing list
> > > > rules-users(a)lists.jboss.org
> > > > https://lists.jboss.org/mailman/listinfo/rules-users
> > > >
> > > >
> > > >
> > >
> > >
> > > --
> > > Edson Tirelli
> > > Software Engineer - JBoss Rules Core Developer
> > > Office: +55 11 3529-6000
> > > Mobile: +55 11 9287-5646
> > > JBoss, a division of Red Hat @ www.jboss.com
> > > _______________________________________________
> > > 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
> >
> >
>
>
> --
> Edson Tirelli
> Software Engineer - JBoss Rules Core Developer
> Office: +55 11 3529-6000
> Mobile: +55 11 9287-5646
> JBoss, a division of Red Hat @ www.jboss.com
>
> _______________________________________________
> 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
--
Edson Tirelli
Software Engineer - JBoss Rules Core Developer
Office: +55 11 3529-6000
Mobile: +55 11 9287-5646
JBoss, a division of Red Hat @ www.jboss.com
7:47 a.m.
New subject: Property Change Listener
Folks,
In 4.0.1. When using Property Change Listener, the rule gets executed
twice when the property gets changed in the RHS of the rule, even though
I have defined no-loop in the rule
Is this an expected behavior? I was thinking that it should behave
similarly to the change to the object with no property change listener
with consecutive "update($o)". Which actually together with no-loop end
up in a single execution of the rule.
Thanks,
-Sergey
**********************
** LEGAL DISCLAIMER **
**********************
This E-mail message and any attachments may contain
legally privileged, confidential or proprietary
information. If you are not the intended recipient(s),
or the employee or agent responsible for delivery of
this message to the intended recipient(s), you are
hereby notified that any dissemination, distribution
or copying of this E-mail message is strictly
prohibited. If you have received this message in
error, please immediately notify the sender and
delete this E-mail message from your computer.
8 a.m.
New subject: globals in rule flow's Split
Folks,
When using globals in rule flow's Split I ran into problem that changes
to the global cannot be recognized by the split and it continues to
route the same destination.
F.e. I have a Split with constrains. And a global TestValid object that
has one boolean attribute - hasErrors
global testValid
Split :
- eval(!testValid.isHasErrors()) // to No Errors action
- eval(testValid.isHasErrors()) // to END
So it ends up with always looping to the No Errors Action, even though
Make Errors sets global : testValid.setHasErrors(true)
In my previous example the problem was that I was not using Shadow
Proxy. But now I am and would like to use global in the split condition,
Please advice if it is an expected behavior and I shouldn't be using
global in split conditions...
Thanks,
-Sergey
**********************
** LEGAL DISCLAIMER **
**********************
This E-mail message and any attachments may contain
legally privileged, confidential or proprietary
information. If you are not the intended recipient(s),
or the employee or agent responsible for delivery of
this message to the intended recipient(s), you are
hereby notified that any dissemination, distribution
or copying of this E-mail message is strictly
prohibited. If you have received this message in
error, please immediately notify the sender and
delete this E-mail message from your computer.
11:21 a.m.
New subject: globals in rule flow's Split
Globals should not be used for storing information that needs to be updated. From the
documentation:
Globals are named objects that can be passed in to the rule engine; without needing to
insert them. Most often these are used for static information, or services that are used
in the RHS of a rule, or perhaps a means to return objects from the rule engine. If you
use a global on the LHS of a rule, make sure it is immutable.
So changes to a global are not taking into account in the LHS of rules.
You should insert your TestValid object in your workingMemory and use conditions as
TestValid ( hasErrors == true )
Once we have variable support, you will be able to do exactly what you are trying to do
here by defining a testValid variable.
Kris
----- Original Message -----
From: Manukyan, Sergey
To: Rules Users List
Sent: Wednesday, September 19, 2007 3:00 PM
Subject: [rules-users] globals in rule flow's Split
Folks,
When using globals in rule flow's Split I ran into problem that changes to the
global cannot be recognized by the split and it continues to route the same destination.
F.e. I have a Split with constrains. And a global TestValid object that has one boolean
attribute - hasErrors
global testValid
Split :
- eval(!testValid.isHasErrors()) // to No Errors action
- eval(testValid.isHasErrors()) // to END
So it ends up with always looping to the No Errors Action, even though Make Errors sets
global : testValid.setHasErrors(true)
In my previous example the problem was that I was not using Shadow Proxy. But now I am
and would like to use global in the split condition,
Please advice if it is an expected behavior and I shouldn't be using global in split
conditions.
Thanks,
-Sergey
**********************
** LEGAL DISCLAIMER **
**********************
This E-mail message and any attachments may contain
legally privileged, confidential or proprietary
information. If you are not the intended recipient(s),
or the employee or agent responsible for delivery of
this message to the intended recipient(s), you are
hereby notified that any dissemination, distribution
or copying of this E-mail message is strictly
prohibited. If you have received this message in
error, please immediately notify the sender and
delete this E-mail message from your computer.
------------------------------------------------------------------------------
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
6078
days inactive
6079
days old
9 comments
4 participants
participants (4)
-
Chris West -
Edson Tirelli -
Kris Verlaenen -
Manukyan, Sergey