[jboss-jira] [JBoss JIRA] (JBRULES-3504) Ruleflow groups are deactivating before firing the last activation in the group

RH Bugzilla Integration (JIRA) jira-events at lists.jboss.org
Fri May 11 16:16:18 EDT 2012


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

RH Bugzilla Integration commented on JBRULES-3504:
--------------------------------------------------

Edson Tirelli <etirelli at redhat.com> made a comment on [bug 821085|https://bugzilla.redhat.com/show_bug.cgi?id=821085]

Requesting blocker status for BRMS 5.3.0 release as this regression is critical.
                
> Ruleflow groups are deactivating before firing the last activation in the group
> -------------------------------------------------------------------------------
>
>                 Key: JBRULES-3504
>                 URL: https://issues.jboss.org/browse/JBRULES-3504
>             Project: Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-core
>    Affects Versions: 5.3.1.Final, 5.4.0.CR1
>            Reporter: Edson Tirelli
>            Assignee: Edson Tirelli
>             Fix For: 5.4.0.Final, 5.5.0.Beta1
>
>
> The fix to JBRULES-3374 introduced a regression where the ruleflow group was being deactivated before firing the last activation in the group. This is wrong, among other things, because that activation can execute working memory actions that might activate other rules in the same group, in which case the ruleflow group should not be deactivated in the first place.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the jboss-jira mailing list