[jboss-jira] [JBoss JIRA] Commented: (JBRULES-1804) Logical insertion lingers after the rule that inserted it no longer supports it (with testcase patch)

[Mark Proctor (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBRULES-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12434295#action_12434295 ] 

Mark Proctor commented on JBRULES-1804:
---------------------------------------

Geoffrey, isn't this what we discussed many months ago? Where I said it wasn't a bug, but maybe just a different approach, but one that would be very hard for us to code for, as it's non trivial, so unlikely we will fix as a priority :(
Jess approach is to not preserve a logical assertion on a modify, so when you do a modify on the retract part of the modify all the logical assertions are removed too, and won't be re-added until the consequence fires. We could possible allow this, would that suffice?

> 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