<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Greg Barton wrote:
<blockquote cite="mid:2234.68508.qm@web81504.mail.mud.yahoo.com"
type="cite">
<pre wrap="">I thought drools had this. If you point me in the right direction (and you have the time) I'd be happy to work on that.
</pre>
</blockquote>
It's non-trivial, especially when evals are involved, but you are
welcome to have a go. Not even sure where to begin on this....<br>
I imagine the first thing is that the PropagationContext will need a
binary mask, supplied by the modify keyword, which shows the fields
modified as part of the modify action. We will then need to do bitmap
masking to determine whether a propagation should continue down a route
or not. This may be an easier one to do on irc, if you can get there.
Just be aware that this is many days, if not weeks work, to get it
right with adequate unit testing.<br>
<br>
Mark<br>
<blockquote cite="mid:2234.68508.qm@web81504.mail.mud.yahoo.com"
type="cite">
<pre wrap="">
--- On Tue, 11/4/08, Edson Tirelli <a class="moz-txt-link-rfc2396E" href="mailto:tirelli@post.com"><tirelli@post.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">From: Edson Tirelli <a class="moz-txt-link-rfc2396E" href="mailto:tirelli@post.com"><tirelli@post.com></a>
Subject: Re: [rules-users] Chart notation, update, and infinite loops
To: "Rules Users List" <a class="moz-txt-link-rfc2396E" href="mailto:rules-users@lists.jboss.org"><rules-users@lists.jboss.org></a>
Date: Tuesday, November 4, 2008, 7:06 PM
Dan,
This is a feature that is in our to-do list. Jess calls
it "slot specific
updates". We did not had the time yet to implement it
though. :(
[]s
Edson
2008/11/4 Dan Seaver <a class="moz-txt-link-rfc2396E" href="mailto:dan.seaver@ge.com"><dan.seaver@ge.com></a>
</pre>
<blockquote type="cite">
<pre wrap="">Your understanding is very close to what I'm
</pre>
</blockquote>
<pre wrap="">looking for. I don't mind
</pre>
<blockquote type="cite">
<pre wrap="">having
multiple rule activations in other areas of the
</pre>
</blockquote>
<pre wrap="">ruleset when the Fact is
</pre>
<blockquote type="cite">
<pre wrap="">updated, I just don't want the current rule, the
</pre>
</blockquote>
<pre wrap="">one with the update
</pre>
<blockquote type="cite">
<pre wrap="">statement, to be reactivated.
Accumulate plus no-loop works fine for the specific
</pre>
</blockquote>
<pre wrap="">case of updating
</pre>
<blockquote type="cite">
<pre wrap="">amounts, but I'd like to have something generic
</pre>
</blockquote>
<pre wrap="">for more sophisticated
</pre>
<blockquote type="cite">
<pre wrap="">logic
that would be implemented in the "then"
</pre>
</blockquote>
<pre wrap="">clause.
</pre>
<blockquote type="cite">
<pre wrap="">Maybe if there was something that looked specifically
</pre>
</blockquote>
<pre wrap="">at each property of
</pre>
<blockquote type="cite">
<pre wrap="">the update? In this case, the "when" clause
</pre>
</blockquote>
<pre wrap="">is looking at the "name"
</pre>
<blockquote type="cite">
<pre wrap="">property and the "then" clause is updating
</pre>
</blockquote>
<pre wrap="">the "amount" property. As the
</pre>
<blockquote type="cite">
<pre wrap="">"name" is not being changed, then the update
</pre>
</blockquote>
<pre wrap="">wouldn't reactivate the rule.
</pre>
<blockquote type="cite">
<pre wrap="">
Greg Barton wrote:
</pre>
<blockquote type="cite">
<pre wrap="">If you have the control fact that handles the
</pre>
</blockquote>
</blockquote>
<pre wrap="">"applied == false"
</pre>
<blockquote type="cite">
<pre wrap="">condition
</pre>
<blockquote type="cite">
<pre wrap="">you wouldn't need to prevent reactivation of
</pre>
</blockquote>
</blockquote>
<pre wrap="">the rule. It would be
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">handled by the condition.
I'm thinking Edson's accumulate
</pre>
</blockquote>
</blockquote>
<pre wrap="">suggestion would be best, at this point.
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">If I understand correctly, what you want is this:
1) One rule Fact/Charge activation per Charge
</pre>
</blockquote>
</blockquote>
<pre wrap="">instance, with no
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">reactivation when the Fact is updated.
2) Other Fact dependent rule activations when the
</pre>
</blockquote>
</blockquote>
<pre wrap="">Fact is updated.
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">The problem with making (1) happen is that
</pre>
</blockquote>
</blockquote>
<pre wrap="">you'd still have the matched
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">Fact being updated once per Charge, which could
</pre>
</blockquote>
</blockquote>
<pre wrap="">lead to reactivation of
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">the rules in (2) multiple times, which you may
</pre>
</blockquote>
</blockquote>
<pre wrap="">not want. If you use
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">accumulate in the Fact/Charge rule, plus no-loop
</pre>
</blockquote>
</blockquote>
<pre wrap="">to prevent reactivation,
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">you get the best of both worlds: single
</pre>
</blockquote>
</blockquote>
<pre wrap="">activation of the Fact/Charge
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">rule, with a single update to notify other rules
</pre>
</blockquote>
</blockquote>
<pre wrap="">that the Fact has
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">changed.
I think what you're after is some kind of
</pre>
</blockquote>
</blockquote>
<pre wrap="">"modify group," where multiple
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">calls to modify are counted as just one, and
</pre>
</blockquote>
</blockquote>
<pre wrap="">rules are notified when the
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">group is closed out. I'm not sure how that
</pre>
</blockquote>
</blockquote>
<pre wrap="">would be implemented, because
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">how do you know when the modifications are
</pre>
</blockquote>
</blockquote>
<pre wrap="">finished? A low priority
</pre>
<blockquote type="cite">
<pre wrap="">rule,
</pre>
<blockquote type="cite">
<pre wrap="">possibly? Anyway, it doesn't exist in
</pre>
</blockquote>
</blockquote>
<pre wrap="">drools, afaik.
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">You could do that kind of thing with an
</pre>
</blockquote>
</blockquote>
<pre wrap="">additional rule that tests for
</pre>
<blockquote type="cite">
<pre wrap="">the
</pre>
<blockquote type="cite">
<pre wrap="">nonexistence of an unprocessed Charge, then does
</pre>
</blockquote>
</blockquote>
<pre wrap="">the update. Adding in
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">the control fact for tracking Charges:
rule "Update Amount"
when
amountFact : Fact(name ==
</pre>
</blockquote>
</blockquote>
<pre wrap="">"Amount")
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> $charge : Charge()
chargeTracker : ChargeTracker(charge ==
</pre>
</blockquote>
</blockquote>
<pre wrap="">$charge, applied == false)
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> then
Double amount = amountFact.getAmount();
Double chargeAmount = charge.getAmount();
amountFact.setAmount(amount +
</pre>
</blockquote>
</blockquote>
<pre wrap="">chargeAmount);
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> chargeTracker.setApplied(true);
update(charge);
end
rule "Close Facts After Charges
</pre>
</blockquote>
</blockquote>
<pre wrap="">Applied"
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> no-loop false
when
amountFact : Fact(name ==
</pre>
</blockquote>
</blockquote>
<pre wrap="">"Amount")
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> not ChargeTracker(applied == false)
then
update(amountFact);
end
You'd probablt also have to prevent the
</pre>
</blockquote>
</blockquote>
<pre wrap="">"Close Facts" rule from firing
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">when there's just no ChargeTrackers in
</pre>
</blockquote>
</blockquote>
<pre wrap="">working memory, too.
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">Give that a try.
--- On Tue, 11/4/08, Dan Seaver
</pre>
</blockquote>
</blockquote>
<pre wrap=""><a class="moz-txt-link-rfc2396E" href="mailto:dan.seaver@ge.com"><dan.seaver@ge.com></a> wrote:
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">From: Dan Seaver <a class="moz-txt-link-rfc2396E" href="mailto:dan.seaver@ge.com"><dan.seaver@ge.com></a>
Subject: Re: [rules-users] Chart notation,
</pre>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">update, and infinite loops
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">To: <a class="moz-txt-link-abbreviated" href="mailto:rules-users@lists.jboss.org">rules-users@lists.jboss.org</a>
Date: Tuesday, November 4, 2008, 1:55 PM
Greg,
1) Yes, in this case I'm looking for the
</pre>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">cartesian
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">join.
2) No, I can't add a property to Charge
</pre>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">as it's
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">part of our corp Object
Model.
However, I could create a third object that
</pre>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">manages whether
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">the Charge has
been processed which works just fine. Unless
</pre>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">there is a
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">simpler strategy /
technique, I'll go with that.
Do you know of any way to keep the rule from
</pre>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">being put back
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">on the agenda
when amountFact is updated? I want other
</pre>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">rules to know that
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">it's been
updated, just not the rule that made the
</pre>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">change.
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">Dan
Greg Barton wrote:
</pre>
<blockquote type="cite">
<pre wrap="">1) Do you want to apply all Charges in
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">working memory
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">to all "Amount"
</pre>
<blockquote type="cite">
<pre wrap="">Facts? I ask because the rule is a
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">cartesian join
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">(i.e. no relation
</pre>
<blockquote type="cite">
<pre wrap="">between matched objects) and that
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">sometimes performs
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">in ways users don't
</pre>
<blockquote type="cite">
<pre wrap="">expect. (i.e. all combinations of
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">objects that match
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">the conditions are
</pre>
<blockquote type="cite">
<pre wrap="">affected by the rule)
2) Can you add a property to the Charge
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">object? Then
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">you could use a
</pre>
<blockquote type="cite">
<pre wrap="">boolean named "applied" to
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">prevent future
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">matches.
</pre>
<blockquote type="cite">
<pre wrap="">Rule "Update Amount"
when
amountFact : Fact(name ==
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">"Amount")
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> charge : Charge(applied == false)
then
Double amount =
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">amountFact.getAmount();
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> Double chargeAmount =
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">charge.getAmount();
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> amountFact.setAmount(amount +
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">chargeAmount);
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> update(amountFact);
charge.setApplied(true);
update(charge);
end
If a charge could be applied to multiple
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">Facts you
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">could maintain an
</pre>
<blockquote type="cite">
<pre wrap="">"appliedTo" list of Facts in
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">the Charge, and
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">check that instead of a
</pre>
<blockquote type="cite">
<pre wrap="">simple boolean.
--- On Tue, 11/4/08, Dan Seaver
</pre>
</blockquote>
<pre wrap=""><a class="moz-txt-link-rfc2396E" href="mailto:dan.seaver@ge.com"><dan.seaver@ge.com></a> wrote:
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">From: Dan Seaver
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap=""><a class="moz-txt-link-rfc2396E" href="mailto:dan.seaver@ge.com"><dan.seaver@ge.com></a>
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">Subject: [rules-users] Chart
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">notation, update, and
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">infinite loops
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">To: <a class="moz-txt-link-abbreviated" href="mailto:rules-users@lists.jboss.org">rules-users@lists.jboss.org</a>
Date: Tuesday, November 4, 2008,
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">11:50 AM
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">I'm trying to find a good
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">technique for
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">updating
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">specific facts in working
memory. What I'm currently doing
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">is something
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">like
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">this:
Rule "Update Amount"
when
amountFact : Fact(name ==
</pre>
</blockquote>
</blockquote>
<pre wrap="">"Amount")
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> charge : Charge()
then
Double amount =
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">amountFact.getAmount();
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> Double chargeAmount =
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">charge.getAmount();
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> amountFact.setAmount(amount +
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">chargeAmount);
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> update(amountFact);
end
The update statement causes an
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">infinite loop.
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">I tried using no-loop, which works
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">if there is 1
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">charge,
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">but not if there
are more than one.
Any help with solutions or
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">strategies would be
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">much
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">appreciated.
--
View this message in context:
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap=""><a class="moz-txt-link-freetext" href="http://www.nabble.com/Chart-notation%2C-update%2C-and-infinite-loops-tp20327483p20327483.html">http://www.nabble.com/Chart-notation%2C-update%2C-and-infinite-loops-tp20327483p20327483.html</a>
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">Sent from the drools - user mailing
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">list archive
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">at
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">Nabble.com.
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">_______________________________________________
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">rules-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:rules-users@lists.jboss.org">rules-users@lists.jboss.org</a>
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap=""><a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/rules-users">https://lists.jboss.org/mailman/listinfo/rules-users</a>
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">_______________________________________________
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">rules-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:rules-users@lists.jboss.org">rules-users@lists.jboss.org</a>
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap=""><a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/rules-users">https://lists.jboss.org/mailman/listinfo/rules-users</a>
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">
</pre>
</blockquote>
<pre wrap="">--
View this message in context:
</pre>
</blockquote>
</blockquote>
</blockquote>
<pre wrap=""><a class="moz-txt-link-freetext" href="http://www.nabble.com/Chart-notation%2C-update%2C-and-infinite-loops-tp20327483p20329780.html">http://www.nabble.com/Chart-notation%2C-update%2C-and-infinite-loops-tp20327483p20329780.html</a>
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">Sent from the drools - user mailing list
</pre>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">archive at
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">Nabble.com.
</pre>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">_______________________________________________
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">rules-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:rules-users@lists.jboss.org">rules-users@lists.jboss.org</a>
</pre>
</blockquote>
</blockquote>
</blockquote>
<pre wrap=""><a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/rules-users">https://lists.jboss.org/mailman/listinfo/rules-users</a>
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">
_______________________________________________
rules-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:rules-users@lists.jboss.org">rules-users@lists.jboss.org</a>
</pre>
</blockquote>
</blockquote>
<pre wrap=""><a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/rules-users">https://lists.jboss.org/mailman/listinfo/rules-users</a>
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">
</pre>
</blockquote>
<pre wrap="">--
View this message in context:
</pre>
</blockquote>
<pre wrap=""><a class="moz-txt-link-freetext" href="http://www.nabble.com/Chart-notation%2C-update%2C-and-infinite-loops-tp20327483p20334594.html">http://www.nabble.com/Chart-notation%2C-update%2C-and-infinite-loops-tp20327483p20334594.html</a>
</pre>
<blockquote type="cite">
<pre wrap="">Sent from the drools - user mailing list archive at
</pre>
</blockquote>
<pre wrap="">Nabble.com.
</pre>
<blockquote type="cite">
<pre wrap="">_______________________________________________
rules-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:rules-users@lists.jboss.org">rules-users@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/rules-users">https://lists.jboss.org/mailman/listinfo/rules-users</a>
</pre>
</blockquote>
<pre wrap="">
--
Edson Tirelli
JBoss Drools Core Development
JBoss, a division of Red Hat @ <a class="moz-txt-link-abbreviated" href="http://www.jboss.com">www.jboss.com</a>
_______________________________________________
rules-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:rules-users@lists.jboss.org">rules-users@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/rules-users">https://lists.jboss.org/mailman/listinfo/rules-users</a>
</pre>
</blockquote>
<pre wrap=""><!---->
_______________________________________________
rules-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:rules-users@lists.jboss.org">rules-users@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/rules-users">https://lists.jboss.org/mailman/listinfo/rules-users</a>
</pre>
</blockquote>
<br>
</body>
</html>