[ https://jira.jboss.org/jira/browse/JBRULES-1881?page=com.atlassian.jira.p... ] Edson Tirelli updated JBRULES-1881: ----------------------------------- Workaround Description: The work around for you is to avoid the use of "from" together with "no-loop" and "lock-on-active". In your example, you could use nested accessors: rule ... when $edi : EdiProduct( product.classificationCode == null, product.pricing.msrp.asBigDecimal > 0 ) then ... end Workaround: [Workaround Exists] -- 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

[ https://jira.jboss.org/jira/browse/JBRULES-1881?page=com.atlassian.jira.p... ] Edson Tirelli commented on JBRULES-1881: ---------------------------------------- The problem happens because you are using "from". There is a whole explanation in the "from" part of the manual regarding the interaction between "from" and the attributes "no-loop" and "lock-on-active", but being brief, the result of a "from" call is a black box for the engine. So, every time the expression of "from" is re-evaluated, it will create new fact handles for the results. So in your example, modifying $edi, will cause the expression "$prod" to be re-evaluated, creating a new fact handle for the result. This means that when the rule is re-activated, since the fact handles in the tuple are different from the previous ones, the no-loop will *not* prevent the activation. This is a behavior that can not be changed now. I will mark this issue as FUTURE because hopefully we can improve it when we develop a feature called "true modify". The work around for you is to avoid the use of "from" together with "no-loop" and "lock-on-active". In your example, you could use nested accessors: rule ... when $edi : EdiProduct( product.classificationCode == null, product.pricing.msrp.asBigDecimal > 0 ) then ... end -- 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

[ https://jira.jboss.org/browse/JBRULES-1881?page=com.atlassian.jira.plugin... ] Mark Proctor resolved JBRULES-1881. ----------------------------------- Fix Version/s: 5.1.0.CR1 (was: FUTURE) Resolution: Done Not heard anything back, so closing this off. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira