RE: [rules-users] advice is needed: rule based processing ofinter connected facts

Thanks for the tip, Edson. Looks promising. Can you give some more details on the following: - JBRules 3.1 is the DROOLS 3.1 (which is currently under dev-t), correct? - Is there a way to achieve the same functionality using existing release (unless DROOLS 3.1 would be released within next month or so)? - The '$' prefixed variables have some special meaning, correct? What section of the manual can I find more details on what it means? (is it part of Drools 3.0 or 3.1 only?) - Performance-wise, would DROOLS (or any other RETE based engine) give any substantial benefit vs plain 'line-by-line' processing of the rules (eg, implemented in SQL, providing facts are loaded from the DB)? Ie, putting aside 'configurability' aspect. And providing there are around 400 'templated' rules, each having ~15 fields/conditions to be analyzed? I can understand how DROOLS can optimize 'static' network (when facts are evaluated against static conditions), but not sure if the same would be valid when facts are evaluated against each other. Thanks. Vlad -----Original Message----- From: rules-users-bounces(a)lists.jboss.org [mailto:rules-users-bounces@lists.jboss.org] On Behalf Of Edson Tirelli Sent: 02 February 2007 11:13 To: Rules Users List Subject: Re: [rules-users] advice is needed: rule based processing ofinter connected facts Hi Vlad, This is a case where you can apply business rules with good results. In the end, it all depends on how you model your Business Objects, but lets get some examples: My understanding is that you are validating your accounting plan, so you may have an Account object in your model. So, if you want to report inconsistencies, you can do something like: rule "missing accounts" when $a : Account( $number : number -> ( number % 10 < 5 ), number < 9000 ) not Account( number == ( $number + 1000 ) ) then // $a does not have a matching primary account end Please, note that the "formulas" I used above may not be the best way to do it... they are only a possible representation of what you said. Here, it seems you are refering to a set of transactions, so you might have a set of transaction objects to represent the transaction in your sample. So, a possible representation would be: rule "transaction consistency" when Transaction( $id : id ) $credits: Double( ) from accumulate( TransactionEntry( id == $id, operation == "credit", $amount : amount ), init( double balance = 0 ), action( balance += $amount ), result( new Double( balance ) ) ); $debits: Double( ) from accumulate( TransactionEntry( id == $id, operation == "debit", $amount : amount ), init( double balance = 0 ), action( balance -= $amount ), result( new Double( balance ) ) ); eval( ! $credits.equals( $debits ) ) then // inconsistency for transaction $id end Again, this is not the only way or the best way... it is just an example. Also, for the above examples, I used syntax/features of the jbrules 3.1 version. Hope it helps. []s Edson Olenin, Vladimir (MOH) wrote: of 400 the -- Edson Tirelli Software Engineer - JBoss Rules Core Developer Office: +55 11 3124-6000 Mobile: +55 11 9218-4151 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