[
https://jira.jboss.org/browse/JBESB-2882?page=com.atlassian.jira.plugin.s...
]
David Ward closed JBESB-2882.
-----------------------------
Resolution: Done
Committed revision 34210. (trunk)
Thew new property is:
ruleFireMethod=FIRE_ALL_RULES or FIRE_UNTIL_HALT.
Description of these properties are in detail in the Services Guide, as well as in javadoc
and lightly in Programmers Guide.
Note that FIRE_UNTIL_HALT blocks the current thread, so a new Thread (with the correct
context class loader) is spawned to call fireUntilHalt(). When someone sends in a Message
that specifies dispose as a Message property, halt() is called on the session, which kills
the spawned thread. The thread is a daemon thread, so it will not keep jboss from
shutting down if it is stopped.
Add support for fireUntilHalt to BusinessRulesProcessor
-------------------------------------------------------
Key: JBESB-2882
URL:
https://jira.jboss.org/browse/JBESB-2882
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 4.6
Reporter: Jeff DeLong
Assignee: David Ward
Fix For: 4.9
To better support CEP, an ESB Rule Service should be able to create the KnowledgeBase,
StatefulKnowledgeSession, etc, and then execute fireUntilHalt. This will cause the thread
to block, and the rules engine will continue to process (in a separate thread). Either the
same ESB Service, or different service with access to the StatefulKnowledgeSession, can
then receive messages / events and insert them into the StatefulKnowledgeSession.
FireUntil Halt provides two important benefits to a CEP application. First it provides
more timely rules firing. Even more important, it support the case where the absence of
incoming events should cause rules to fire.
--
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