[
https://jira.jboss.org/jira/browse/JBRULES-1804?page=com.atlassian.jira.p...
]
Geoffrey De Smet commented on JBRULES-1804:
-------------------------------------------
Thanks for noticing the typo :) I 've fixed the typo in svn
I don't agree that Sensor should override equals/hashCode so it takes temperature into
account, though a separate test where another testfact does would be interesting too.
My use cases in drools-solver follow the Sensor problem: it's the same Sensor (so
equals isn't affected), it's temperature just changes.
Logical insertion lingers after the rule that inserted it no longer
supports it (with testcase patch)
-----------------------------------------------------------------------------------------------------
Key: JBRULES-1804
URL:
https://jira.jboss.org/jira/browse/JBRULES-1804
Project: JBoss Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-core (expert)
Affects Versions: 5.0.0.M2
Reporter: Geoffrey De Smet
Assignee: Edson Tirelli
Priority: Critical
Fix For: 5.0.0.M3
This one got me headscratching for a while, untill I realized what the problem is.
Tim reported on the mailing list he ran into it to.
I've commmited a testcase in subversion, in TruthMaintenanceTest, called
disabled_testLogicalInsertionsModifySameRuleGivesDifferentLogicalInsertion
Remove the "disabled_" to enable it and try it out.
Here's what happens in the testcase:
3 sensors with tempature 100, 200 and 200 are inserted.
There's a rule which logically inserts all encountered tempatures, so 100 and 200.
Then the first sensor modifies to a tempature of 150.
As it turns out, the encoutered tempatures should be 150 and 200 now, but instead
it's 100, 150 and 200.
Even though there is no sensor that has a tempature of 100.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira