<HTML xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<HEAD><!-- Template generated by Exclaimer Template Editor on 10:58:23 Thursday, 14 February 2013 -->
<STYLE type=text/css>P.2ee1cc27-72fd-41ad-a721-72d082ea8444 {
MARGIN: 0cm 0cm 0pt
}
LI.2ee1cc27-72fd-41ad-a721-72d082ea8444 {
MARGIN: 0cm 0cm 0pt
}
DIV.2ee1cc27-72fd-41ad-a721-72d082ea8444 {
MARGIN: 0cm 0cm 0pt
}
TABLE.2ee1cc27-72fd-41ad-a721-72d082ea8444Table {
MARGIN: 0cm 0cm 0pt
}
DIV.Section1 {
page: Section1
}
</STYLE>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii" />
<meta name="Generator" content="Microsoft Word 12 (filtered medium)" />
<style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"Lucida Console";
panose-1:2 11 6 9 4 5 4 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:14.0pt;
font-family:"Lucida Console";}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Lucida Console";}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</HEAD>
<BODY lang="EN-US" link="blue" vlink="purple">
<P>
<div class="WordSection1">
<p class="MsoPlainText">> We've been through this kind of discussion time and again...<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><span style=font-family:"Calibri","sans-serif";color:#1F497D>Indeed you have. I remember when this forum helped me with my exact same misunderstanding when I was struggling with my very first HelloWorld.DRL.<o:p></o:p></span></p>
<p class="MsoPlainText"><span style=font-family:"Calibri","sans-serif";color:#1F497D><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style=font-family:"Calibri","sans-serif";color:#1F497D>Thank you to this DROOLs forum (and especially Wolfgang) for being so gentle and generous when helping the DROOLs newbie – each of us – time and again (and again) … in this
specific regard.<o:p></o:p></span></p>
<p class="MsoPlainText"><span style=font-family:"Calibri","sans-serif";color:#1F497D><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style=font-family:"Calibri","sans-serif";color:#1F497D>Despite it being monotonous at each encounter, please continue to gift us this help – at this exact stage in our development -- for as long as you possibly can. For you
it must be like the equivalent of “changing diapers” for each and every newbie “born” into the DROOLs community. Beyond monotonous, it must be outright unpleasant. But this help --at this stage -- is exactly what it takes for the DROOLs community to “go
forth and multiply”. <o:p></o:p></span></p>
<p class="MsoPlainText"><span style=font-family:"Calibri","sans-serif";color:#1F497D><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style=font-family:"Calibri","sans-serif";color:#1F497D>One day, those of us that you helped now will help others later… in the exact same way … time and again (and again!).<o:p></o:p></span></p>
<p class="MsoPlainText"><span style=font-family:"Calibri","sans-serif";color:#1F497D><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style=font-family:"Calibri","sans-serif";color:#1F497D>Of course you must know this … it is likely exactly why you do it … a sort of DROOLs paternal instinct.
</span><span style=font-family:Wingdings;color:#1F497D>J</span><span style=font-family:"Calibri","sans-serif";color:#1F497D><o:p></o:p></span></p>
<p class="MsoPlainText"><span style=font-family:"Calibri","sans-serif";color:#1F497D><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style=font-family:"Calibri","sans-serif";color:#1F497D>But even if you do know this, it is important that you know it is appreciated.<o:p></o:p></span></p>
<p class="MsoPlainText"><span style=font-family:"Calibri","sans-serif";color:#1F497D><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style=font-family:"Calibri","sans-serif";color:#1F497D>Thank You. Emphatically, thank you.<o:p></o:p></span></p>
<p class="MsoPlainText"><span style=color:#1F497D><o:p> </o:p></span></p>
<p class="MsoPlainText">-----Original Message-----<br />
From: rules-users-bounces@lists.jboss.org [mailto:rules-users-bounces@lists.jboss.org] On Behalf Of Wolfgang Laun<br />
Sent: Wednesday, February 13, 2013 6:01 AM<br />
To: Rules Users List<br />
Subject: Re: [rules-users] Evaluate rules for multiple facts of the same type within a StateuflSession<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">We've been through this kind of discussion time and again...<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Check whether procedural programming isn't better suited for your task whenever you shy away from the requirements and benefits of a rule based solution.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">And see the section on "Fact Classification" in my whitepaper:<o:p></o:p></p>
<p class="MsoPlainText"><a href="https://engage.redhat.com/forms/rule-design-patterns"><span style=color:windowtext;text-decoration:none>https://engage.redhat.com/forms/rule-design-patterns</span></a><o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">-W<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">On 13/02/2013, pdario <<a href="mailto:dario.piantanida@gmail.com"><span style=color:windowtext;text-decoration:none>dario.piantanida@gmail.com</span></a>> wrote:<o:p></o:p></p>
<p class="MsoPlainText">> I'm sorry, it's not clear.<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> Do you mean I have to add a condition in each rule to check whether
<o:p></o:p></p>
<p class="MsoPlainText">> other discount have been already applied?<o:p></o:p></p>
<p class="MsoPlainText">> Even so, I can I control the preferred order of the discounts without
<o:p></o:p></p>
<p class="MsoPlainText">> salience? Do I have to put negated conditions of each rule??<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> It looks cumbersome...<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> --<o:p></o:p></p>
<p class="MsoPlainText">> View this message in context:<o:p></o:p></p>
<p class="MsoPlainText">> <a href="http://drools.46999.n3.nabble.com/Evaluate-rules-for-multiple-facts-of">
<span style=color:windowtext;text-decoration:none>http://drools.46999.n3.nabble.com/Evaluate-rules-for-multiple-facts-of</span></a><o:p></o:p></p>
<p class="MsoPlainText">> -the-same-type-within-a-StateuflSession-tp4022157p4022270.html<o:p></o:p></p>
<p class="MsoPlainText">> Sent from the Drools: User forum mailing list archive at Nabble.com.<o:p></o:p></p>
<p class="MsoPlainText">> _______________________________________________<o:p></o:p></p>
<p class="MsoPlainText">> rules-users mailing list<o:p></o:p></p>
<p class="MsoPlainText">> <a href="mailto:rules-users@lists.jboss.org"><span style=color:windowtext;text-decoration:none>rules-users@lists.jboss.org</span></a><o:p></o:p></p>
<p class="MsoPlainText">> <a href="https://lists.jboss.org/mailman/listinfo/rules-users">
<span style=color:windowtext;text-decoration:none>https://lists.jboss.org/mailman/listinfo/rules-users</span></a><o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">_______________________________________________<o:p></o:p></p>
<p class="MsoPlainText">rules-users mailing list<o:p></o:p></p>
<p class="MsoPlainText"><a href="mailto:rules-users@lists.jboss.org"><span style=color:windowtext;text-decoration:none>rules-users@lists.jboss.org</span></a><o:p></o:p></p>
<p class="MsoPlainText"><a href="https://lists.jboss.org/mailman/listinfo/rules-users"><span style=color:windowtext;text-decoration:none>https://lists.jboss.org/mailman/listinfo/rules-users</span></a><o:p></o:p></p>
</div>
<BR /><BR />
<HR id=HR1 />
<BR /><SPAN style="FONT-FAMILY: Arial; COLOR: #808080; FONT-SIZE: 7.5pt">NOTICE:
Morgan Stanley is not acting as a municipal advisor and the opinions or views
contained herein are not intended to be, and do not constitute, advice within
the meaning of Section 975 of the Dodd-Frank Wall Street Reform and Consumer
Protection Act. If you have received this communication in error, please destroy
all electronic and paper copies and notify the sender immediately.
Mistransmission is not intended to waive confidentiality or privilege. Morgan
Stanley reserves the right, to the extent permitted under applicable law, to
monitor electronic communications. This message is subject to terms available at
the following link: <A style="FONT-FAMILY: Arial; COLOR: #808080; FONT-SIZE: 7.5pt" href="http://www.morganstanley.com/disclaimers">http://www.morganstanley.com/disclaimers</A>
If you cannot access these links, please notify us by reply message and we will
send the contents to you. By messaging with Morgan Stanley you consent to the
foregoing.</SPAN><BR />
<P></P>
<P></P></P></BODY>
</HTML>