[
http://jira.jboss.com/jira/browse/JBRULES-1152?page=comments#action_12377153 ]
Edson Tirelli commented on JBRULES-1152:
----------------------------------------
Steve, I'm not sure what is happening, as I downloaded your v2 example, added drools
dependencies and it is running fine (only 1 rule firing), doesn't matter the order of
the statements in the consequence. I tried both 4.0.1 and current trunk versions (revision
#15173).
Please note that the order of the statements does matter when using PropertyChangeSupport
as you are doing, because your bean is firing the update event for every single change in
the bean. So, changing the attributes in the following order:
$acu.setMessage("on");
$acu.setState(false);
Is heavier than doing:
$acu.setState(false);
$acu.setMessage("on");
This is why we advise against the use of dynamic beans in such scenarios. Please take a
look in the new MVEL modify feature for composite attribute changes, or the use of
explicit update() calls.
Although, even if you use the dynamic beans in the way you are doing, only one rule should
fire, and that is the behavior I'm seeing using your project.
Also worth of note is that apparently you are using old dependencies in this example
project that are not needed anymore. Before releasing the 4.0 version we did a
dependencies cleanup to avoid the need of several libraries that were previously transient
dependencies of drools dependencies. For an update documentation of currently required
dependencies, please read the README_DEPENDENCIES.txt doc in drools release zip.
my unit tests are hanging with drools 4.0.1
-------------------------------------------
Key: JBRULES-1152
URL:
http://jira.jboss.com/jira/browse/JBRULES-1152
Project: JBoss Rules
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 4.0.1
Environment: Java 1.5, Mac OX X 10.4.10, Drools 4.0.1
Reporter: Steve Miner
Assigned To: Edson Tirelli
Fix For: 4.0.2
Attachments: drools1152-v2.zip, drools1152.zip
Sorry, I don't have very specific information. Some of my project's unit tests
are hanging with drools 4.0.1. No error, just not completing. I tried to debug a bit but
could not figure it out. Consider this an early warning until I can gather more info.
Everything worked fine with 4.0 so I went back to that.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira