[jboss-jira] [JBoss JIRA] Resolved: (JBRULES-318) eval() not re-evaluated when objects were modified

[Edson Tirelli (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBRULES-318?page=all ]

Edson Tirelli resolved JBRULES-318.
-----------------------------------

    Fix Version/s: 3.0.3
                       (was: 3.0.2)
       Resolution: Done

In addition to fix JoinNode.modifyTuple() as I did previously, a fix to JoinNode.modifyObject() also had to be done. 

The problem is that when a node is removed from a linked list, its "previous" and "next" references are nulled out and the modifyObject() method was not taking that in account.

Let me know if you find any other problem.

Commited in revision #5052.

Edson

> eval() not re-evaluated when objects were modified
> --------------------------------------------------
>
>                 Key: JBRULES-318
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-318
>             Project: JBoss Rules
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.0.1
>         Environment: JBossRules 3.0.1
> Eclipse 3.2 rc7
> JDK 5
>            Reporter: Jean-Pierre GRILLON
>         Assigned To: Edson Tirelli
>             Fix For: 3.0.3
>
>         Attachments: Drools-eval.zip
>
>
> I face a problem (bug?): I have a condition using ?eval? which doesn?t seem to be reevaluated when objects are modified.
> The class NumberTest wraps a number (field nb) and the index (field index).
> The rule gets 2 NumberTest, the first number is greater than the second one ; and the eval condition should test that the first index is less than the second. But the rule is fired even if this condition is not fulfilled (see the check function).

-- 
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