[
https://issues.redhat.com/browse/DROOLS-5135?page=com.atlassian.jira.plug...
]
Mario Fusco resolved DROOLS-5135.
---------------------------------
Resolution: Rejected
Drools DRL is a strongly typed language.
As an exercise, let's try to do a similar exercise on what you're suggesting in
Java. What you're asking is the equivalent of "I have a class Foo with, among
other things, a method bar() that is called by other classes. I remove the method bar()
and I would like my program, at least in the classes not using that method bar(), to work
normally".
In my opinion this requirement doesn't make much sense and, in the same way as the
whole Java program cannot be compiled if there are still classes referencing that method
bar(), so Drools cannot compile the whole rules base and generate its internal
datastructures, necessary to evaluate those rules if any of them is malformed or
references not existing types or properties.
Drools Setup › Exception Handling in Drools Rule Condition
-----------------------------------------------------------
Key: DROOLS-5135
URL:
https://issues.redhat.com/browse/DROOLS-5135
Project: Drools
Issue Type: Bug
Components: Guided Rule Editor
Affects Versions: 7.15.0.Final
Reporter: Bishnu Shankar Pandey
Assignee: Mario Fusco
Priority: Major
How can we do rule wise exception handling in the drools rule condition? My scenario is
how to handle scenarios when the schema of an event changes.
For example, let's say Initially I have an event that has 5 members namely
name,num1,num2,num3,num4. I started creating rules for the event and the rule engine is
running for some time. After that let's assume there is a scenario in which one of the
class members (say num4) is removed from the event because of some reason. Now what I can
do now is to change the Event class, but all the rules associated with that member will
give me exceptions. The exceptions will also affect other rules which can run with the
current data. Is there any way to handle exception in rule condition for specific rule and
restrict it to disturb the independent rules.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)