On 16/05/2012, Joe Ammann wrote:
> On 05/16/2012 09:06 AM, Wolfgang Laun wrote:
>> The first rule is called "No action - possibly commented out".
> Had a look at this and I think this will be the way for me: Implement my
> own set of verifier rules. It still don't quite understand how I would
> "
On 05/16/2012 09:06 AM, Wolfgang Laun wrote:
> On 16/05/2012, Joe Ammann wrote:
>> On 05/15/2012 07:24 PM, Wolfgang Laun wrote:
>>> Assuming you can get hold of the resulting DRL text, a simple script
>>> might detect rules where there is nothing between "then" and "end".
>> I have currently imple
On 16/05/2012, Joe Ammann wrote:
> On 05/15/2012 07:24 PM, Wolfgang Laun wrote:
>> Assuming you can get hold of the resulting DRL text, a simple script
>> might detect rules where there is nothing between "then" and "end".
> I have currently implemented something similar. A REST client that
> peri
On 05/15/2012 07:24 PM, Wolfgang Laun wrote:
> Assuming you can get hold of the resulting DRL text, a simple script
> might detect rules where there is nothing between "then" and "end".
I have currently implemented something similar. A REST client that
periodically scans the BRLs in certain Guvnor
Assuming you can get hold of the resulting DRL text, a simple script
might detect rules where there is nothing between "then" and "end".
Otherwise, following the techniques used in the Guvnor's validator,
you can investigate the consequence text and use heuristics to
detect the bad ones.
-W
On
Hi all
I have an ongoing discussion with my users: They have been using several
home-grown rule oriented applications for years. Almost all of these
"rule engines" were built for one very specific reason, and the users
have come accustomed to just specify a LHS of a rule. They never needed
to spec
