[jboss-jira] [JBoss JIRA] Closed: (JBRULES-144) async assert

[Mark Proctor (JIRA)]

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

Mark Proctor closed JBRULES-144.
--------------------------------

    Fix Version/s: 3.1-m2
                       (was: 3.1-m3)
       Resolution: Done
         Assignee: Mark Proctor

StatelessSession and StatefulSession now both support async methods, the thread handling is pluggeable using the ExecutorService interface.

> async assert
> ------------
>
>                 Key: JBRULES-144
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-144
>             Project: JBoss Rules
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Reteoo
>            Reporter: Mark Proctor
>         Assigned To: Mark Proctor
>             Fix For: 3.1-m2
>
>         Attachments: ConcurrentWorkingMemory.java
>
>
> We need an async assert. This means the fact is is asserted and immediately returns. Internally there is a consumer/provider based queue that one by one asserts the stacked items into the working memory. Need ot make sure that users can handle async exceptions.
> There might also be some settings to do with 2 phase commit, in that when do we call fireAllRules? Do we call it after every assertion, after a set time period, after X facts are asserted - or maybe a combination of both? Initially probably esiest to just call fireAllRules on each assertion from the Queue.
> I recommend that thechannel code stuff be "borrowed" from http://gee.cs.oswego.edu/dl/classes/EDU/oswego/cs/dl/util/concurrent/LinkedQueue.html - only take hte classes you need and refactor them for org.drools.util.concurrent.

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