[jboss-jira] [JBoss JIRA] Assigned: (JBRULES-2723) Block fireUntilHalt when a fact is inserted/updated/retracted, until all activations in response are complete

Mark Proctor (JIRA) jira-events at lists.jboss.org
Mon Nov 8 02:17:01 EST 2010


     [ https://jira.jboss.org/browse/JBRULES-2723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Proctor reassigned JBRULES-2723:
-------------------------------------

    Assignee: Edson Tirelli  (was: Mark Proctor)


> Block fireUntilHalt when a fact is inserted/updated/retracted, until all activations in response are complete
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: JBRULES-2723
>                 URL: https://jira.jboss.org/browse/JBRULES-2723
>             Project: Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-core
>    Affects Versions: 5.1.1.FINAL
>            Reporter: Norman Chan
>            Assignee: Edson Tirelli
>
> fireUntilHalt starts executing rule consequences as soon as any rule has been activated.  This can be a problem if an event insertion, etc causes many rules to be activated in response.  The agenda should determine which activated rule is executed first based on rule properties (e.g. salience), but because not all activations are complete when fireUntilHalt starts executing, the rule that is fired first may not be the one that should fire first.
> By blocking fireUntilHalt until all activations in response to a change in working memory are complete, activated rules will be executed in the correct order.

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

        


More information about the jboss-jira mailing list