[
https://issues.jboss.org/browse/DROOLS-931?page=com.atlassian.jira.plugin...
]
Mario Fusco closed DROOLS-931.
------------------------------
Resolution: Rejected
First of all be advised that Drools 4.x and 5.x is no longer supported. Please open
another ticket if you believe there's a related issue on Drools 6.x
What you're saying is that you want determinstic behaviour on arbitrary salience.
Unfortunately that is never guaranteed and it can change between JVMs and between Drools
versions. With Drools 6.x we partially fixed this ambiguity because rules in the same DRL
file have an implicit relative salience (if no explicit salience is given). This means
that rules that appear first in the file have an higher salience than the ones that comes
later. However we still don't have a similar mechanism for rules in different DRL
files so in that case it can go arbitrary again.
Drools 4.0.7
------------
Key: DROOLS-931
URL:
https://issues.jboss.org/browse/DROOLS-931
Project: Drools
Issue Type: Bug
Environment: WAS 6.1(JDK 1.5) & WAS 8.5.5(JDK 1.7)
Reporter: raj S
Assignee: Mario Fusco
We have around 10,000+ rules running on a legacy system which is using jdk 1.5. those
rules doesn't have salience set for all the rules , but have been tested to work fine
with older jdk.
Now are trying to upgrade the system to later version of JDK, rules execution order seems
to be difference ,because they don't have salience set. in the process we have
identified that few rules were having coding issues and corrected them.
Issue: is there a way to grantee the same execution order between the jdk 1.5 & JDK
1.7. we haven't updated the drools version just the JDK. can you please give us some
insight in to the natural order of rules execution in drools engine so we can put in a fix
outside the engine to ensure the same order. any help is appreciated.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)