<font size=2 face="sans-serif">is there a place to go look at a detailed
example?</font>
<br>
<br><font size=2 face="sans-serif">Thanks</font>
<br><font size=2 face="sans-serif">Ghanshyam</font>
<br>
<br>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">Wolfgang Laun <wolfgang.laun@gmail.com></font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">Rules Users List <rules-users@lists.jboss.org>,
</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">11/05/2012 05:19 AM</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">Re: [rules-users]
DROOLs callback API for L-value predicate matching
events</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Sent by:
</font><font size=1 face="sans-serif">rules-users-bounces@lists.jboss.org</font>
<br>
<hr noshade>
<br>
<br>
<br><tt><font size=2>"Learning the reason for failure to match"
is the title of a section in my<br>
boot camp you missed at this year's IntelliFest a couple of weeks ago.<br>
<br>
You are getting close to the solution, but here's the outline of the<br>
rule programming design pattern:<br>
<br>
Write one rule (high salience) to create an auxiliary fact (Aux),<br>
containing a reference to the fact under investigation (Crf) and a<br>
Set.<br>
<br>
Write one rule each, combining Aux and Crf, restricting the latter with
one<br>
of the required property values/range. On the RHS, add an<br>
identification to the set component of Aux. DO NOT MODIFY/UPDATE.<br>
<br>
Write another rule (low salience) combining Aux and Crf and see what<br>
Aux contains in the Set. Retract Aux.<br>
<br>
-W<br>
<br>
<br>
<br>
<br>
On 05/11/2012, Cotton, Ben <Ben.Cotton@morganstanley.com> wrote:<br>
> Could a solution be as simple as this? Is this approach to consuming<br>
> "LCHUS_IRS_CURRENCY_RULE" L-value matching events sound/complete
(and<br>
> not-vulnerable to any race condition?). Is there any DROOLS
EventListener<br>
> callback API that would be more appropriate to solve the problem?<br>
><br>
> E.g. I want to be able to log when each of these 5 L-value predicates<br>
> either "MATCHES" or "FAILS TO MATCH" (at the time
of the event)<br>
><br>
> rule "LCHUS_IRS_CURRENCY_RULE" //XLS Item=195<br>
> when<br>
> IRDCurrencyRuleFact(<br>
> productType == "IRS",<br>
> currency=="GBP",<br>
> upfrontFeePaymentDate < IRDCurrencyRuleFact.terminationDate,<br>
> maturity <= 18275,<br>
>
//unit
= days, i.e. 50 Years<br>
> notional <= 99,999,999,999.99<br>
>
//max Notional<br>
> )<br>
> then<br>
> System.out.println("LCHUS");<br>
> end<br>
><br>
><br>
> Again the objective is to be able to join a high-resolution logging<br>
> capability wrt to which of the specific 5 L-value predicates matched.<br>
> Instinctively, to this DROOLs newbie, this approach seems workable
but not<br>
> ideal ....<br>
><br>
> rule "LCHUS_IRS_CURRENCY_RULE_LVALUE_MATCHING_EVENT_1"<br>
> when<br>
> IRDCurrencyRuleFact(productType == "IRS")<br>
> then<br>
> System.out.println("LCHUS_IRS_CURRENCY_RULE_L-value
event 1<br>
> match"); //log event L-value predicate 1 matched<br>
> end<br>
><br>
> rule "LCHUS_IRS_CURRENCY_RULE_LVALUE_MATCHING_EVENT_2"<br>
> when<br>
> IRDCurrencyRuleFact(currency=="GBP")<br>
> then<br>
> System.out.println("LCHUS_IRS_CURRENCY_RULE_L-value
event 2<br>
> match"); //log event L-value predicate 2 matched<br>
> end<br>
><br>
> rule "LCHUS_IRS_CURRENCY_RULE_LVALUE_MATCHING_EVENT_3"<br>
> when<br>
> IRDCurrencyRuleFact(upfrontFeePaymentDate
<<br>
> IRDCurrencyRuleFact.terminationDate)<br>
> then<br>
> System.out.println("LCHUS_IRS_CURRENCY_RULE_L-value
event 3<br>
> match"); //log event L-value predicate 3 matched<br>
> end<br>
><br>
> rule "LCHUS_IRS_CURRENCY_RULE_LVALUE_MATCHING_EVENT_4"<br>
> when<br>
> IRDCurrencyRuleFact(maturity
<= 18275)<br>
> then<br>
> System.out.println("LCHUS_IRS_CURRENCY_RULE_L-value
event 4<br>
> match"); //log event L-value predicate 4 matched<br>
> end<br>
><br>
> rule "LCHUS_IRS_CURRENCY_RULE_LVALUE_MATCHING_EVENT_5"<br>
> when<br>
> IRDCurrencyRuleFact(notional
<= 99,999,999,999.99)<br>
> then<br>
> System.out.println("LCHUS_IRS_CURRENCY_RULE_L-value
event 5<br>
> match"); //log event L-value predicate 5 matched<br>
> end<br>
><br>
><br>
><br>
><br>
><br>
> Ben D Cotton III<br>
> Morgan Stanley & Co.<br>
> OTC Derivatives Clearing Technology<br>
> 1221 AOTA Rockefeller Ctr - Flr 27<br>
> New York, NY 10020<br>
> (212)762.9094<br>
> ben.cotton@ms.com<</font></tt><a href=mailto:ben.cotton@ms.com><tt><font size=2>mailto:ben.cotton@ms.com</font></tt></a><tt><font size=2>><br>
><br>
><br>
><br>
><br>
> From: rules-users-bounces@lists.jboss.org<br>
> [</font></tt><a href="mailto:rules-users-bounces@lists.jboss.org"><tt><font size=2>mailto:rules-users-bounces@lists.jboss.org</font></tt></a><tt><font size=2>]
On Behalf Of Cotton, Ben<br>
> (ISGT)<br>
> Sent: Saturday, November 03, 2012 8:24 AM<br>
> To: rules-users@lists.jboss.org<br>
> Cc: O'Brien, Patrick (ISGT)<br>
> Subject: [rules-users] DROOLs callback API for L-value predicate matching<br>
> events<br>
><br>
> Hi, Can someone please point me to compelling examples/sample
code of how<br>
> to use a DROOLs callback API for very high-resolution logging of L-value<br>
> predicate matching events?<br>
><br>
> E.g. I want to be able to log when each of these 5 L-value predicates<br>
> either "MATCHES" or "FAILS TO MATCH" (at the time
of the event)<br>
><br>
> rule "LCHUS_IRS_CURRENCY_RULE" //XLS Item=195<br>
> when<br>
> IRDCurrencyRuleFact(<br>
> productType == "IRS",<br>
> currency=="GBP",<br>
> upfrontFeePaymentDate < IRDCurrencyRuleFact.terminationDate,<br>
> maturity <= 18275,<br>
>
//unit
= days, i.e. 50 Years<br>
> notional <= 99,999,999,999.99<br>
>
//max Notional<br>
> )<br>
> then<br>
> System.out.println("LCHUS");<br>
> end<br>
><br>
><br>
> Ben D Cotton III<br>
> Morgan Stanley & Co.<br>
> OTC Derivatives Clearing Technology<br>
> 1221 AOTA Rockefeller Ctr - Flr 27<br>
> New York, NY 10020<br>
> (212)762.9094<br>
> ben.cotton@ms.com<</font></tt><a href=mailto:ben.cotton@ms.com><tt><font size=2>mailto:ben.cotton@ms.com</font></tt></a><tt><font size=2>><br>
><br>
><br>
><br>
> ________________________________<br>
><br>
> NOTICE: Morgan Stanley is not acting as a municipal advisor and the
opinions<br>
> or views contained herein are not intended to be, and do not constitute,<br>
> advice within the meaning of Section 975 of the Dodd-Frank Wall Street<br>
> Reform and Consumer Protection Act. If you have received this communication<br>
> in error, please destroy all electronic and paper copies and notify
the<br>
> sender immediately. Mistransmission is not intended to waive confidentiality<br>
> or privilege. Morgan Stanley reserves the right, to the extent permitted<br>
> under applicable law, to monitor electronic communications. This message
is<br>
> subject to terms available at the following link:<br>
> </font></tt><a href=http://www.morganstanley.com/disclaimers><tt><font size=2>http://www.morganstanley.com/disclaimers</font></tt></a><tt><font size=2>
If you cannot access these links,<br>
> please notify us by reply message and we will send the contents to
you. By<br>
> messaging with Morgan Stanley you consent to the foregoing.<br>
><br>
><br>
> ________________________________<br>
><br>
> NOTICE: Morgan Stanley is not acting as a municipal advisor and the
opinions<br>
> or views contained herein are not intended to be, and do not constitute,<br>
> advice within the meaning of Section 975 of the Dodd-Frank Wall Street<br>
> Reform and Consumer Protection Act. If you have received this communication<br>
> in error, please destroy all electronic and paper copies and notify
the<br>
> sender immediately. Mistransmission is not intended to waive confidentiality<br>
> or privilege. Morgan Stanley reserves the right, to the extent permitted<br>
> under applicable law, to monitor electronic communications. This message
is<br>
> subject to terms available at the following link:<br>
> </font></tt><a href=http://www.morganstanley.com/disclaimers><tt><font size=2>http://www.morganstanley.com/disclaimers</font></tt></a><tt><font size=2>
If you cannot access these links,<br>
> please notify us by reply message and we will send the contents to
you. By<br>
> messaging with Morgan Stanley you consent to the foregoing.<br>
><br>
_______________________________________________<br>
rules-users mailing list<br>
rules-users@lists.jboss.org<br>
</font></tt><a href="https://lists.jboss.org/mailman/listinfo/rules-users"><tt><font size=2>https://lists.jboss.org/mailman/listinfo/rules-users</font></tt></a><tt><font size=2><br>
</font></tt>
<br>
-----------------------------------------
The information contained in this communication (including any
attachments hereto) is confidential and is intended solely for the
personal and confidential use of the individual or entity to whom
it is addressed. If the reader of this message is not the intended
recipient or an agent responsible for delivering it to the intended
recipient, you are hereby notified that you have received this
communication in error and that any review, dissemination, copying,
or unauthorized use of this information, or the taking of any
action in reliance on the contents of this information is strictly
prohibited. If you have received this communication in error,
please notify us immediately by e-mail, and delete the original
message. Thank you