I'm thinking more along the lines of a .DRL code enrichment tool. The tool would take
the burden of generating additional .DRL code
to evaluate all relevant conditions individually and keep track of
the positives
This tool would work entirely outside the Drools rules-engine runtime. The engine would
remain unburdened and optimized. But, if the .DRL author *chose* to deploy his
tool-redered "when do rules fail to fire?" enriched .DRL unto the engine, he
does so with the understanding that he is trading off performance for accounting
precision.
Just like the Drools framework's .DRT capability has the ambition to unburden the .DRL
author of laboriously key-stroking a know pattern from a DataSource, XLS, etc., this
"when do rules fail to fire?" pattern seems to be an important one for those
with detailed accounting/audit use case requirements. But, it is a pattern that is
(currently) a laborious key-stroke intensive "burden" (too strong a word,
probably) for the .DRL author.
Just thinking out loud. Very excited to see what's in Wolfgang's whitepaper.
-----Original Message-----
From: rules-users-bounces(a)lists.jboss.org [mailto:rules-users-bounces@lists.jboss.org] On
Behalf Of Grant Rettke
Sent: Wednesday, January 30, 2013 10:02 AM
To: Rules Users List
Subject: Re: [rules-users] Non short circuit ANDing
On Wed, Jan 30, 2013 at 8:35 AM, Cotton, Ben <Ben.Cotton(a)morganstanley.com> wrote:
Would it be reasonable to suggest that the Drools team provide the
user community with some tool, API, or other framework construct that
might assist us when we are faced with this exact task?
I'm studying rules engines. This desire seems to go 100% against the intent of a rules
engine. That said, maybe what people want is some like a rules engine, but different,
which more such features.
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
--------------------------------------------------------------------------------
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:
http://www.morganstanley.com/disclaimers. 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.