[jboss-jira] [JBoss JIRA] Assigned: (JBRULES-41) Enhance no-loop functionality

[Michael Neale (JIRA)]

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

Michael Neale reassigned JBRULES-41:
------------------------------------

    Assignee: Edson Tirelli  (was: Michael Neale)

Edson, this is low priority, but I thought you may have ideas on this. Its been around for quite a while.

> Enhance no-loop functionality
> -----------------------------
>
>                 Key: JBRULES-41
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-41
>             Project: JBoss Rules
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Rule Assemply/SPI
>    Affects Versions: 3.0-beta1
>            Reporter: Michael Neale
>         Assigned To: Edson Tirelli
>             Fix For: 3.1-m3
>
>   Original Estimate: 3 days
>  Remaining Estimate: 3 days
>
> At present, no-loop is simply limited to stopping a rule firing itself with the same facts.
> A common request I get, whenever visiting anyone, is how to remember all rule activations (rule/fact combinations that have fired in the past) and stop the same happening in the future in a single instance of working memory.
> This can be an option set on a per instance, or per haps per-file basis. By default it must be off, as it will require extra memory to record the history, and I don't think it would be suitable for long lived working memories.
> However, for the pseudo "stateless" pattern (which probably 70-80% of people use) it would be quite safe and beneficial. 

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