[JBoss JIRA] Created: (JBESB-2604) Document registry interceptors
by Aaron Pestel (JIRA)
Document registry interceptors
------------------------------
Key: JBESB-2604
URL: https://jira.jboss.org/jira/browse/JBESB-2604
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Documentation
Environment: SOA-P 4.3 SP1
Reporter: Aaron Pestel
Priority: Minor
This is a request to document the two known registry interceptors: org.jboss.internal.soa.esb.services.registry.InVMRegistryInterceptor and org.jboss.internal.soa.esb.services.registry.CachingRegistryInterceptor
The InVMRegistryInterceptor is listed in the services guide, section 2.1 and 3.2: http://www.redhat.com/docs/en-US/JBoss_SOA_Platform/4.3.CP01/html-single/...
In section 2.1, it shows an extract of the registry portion of the jbossesb-properties.xml - which includes InVMRegistryInterceptor, and then goes on to describe each property, but neglects to describe the org.jboss.soa.esb.registry.interceptors property where InVMRegistryInterceptor is set.
I am requesting a description in section 2.1 of the org.jboss.soa.esb.registry.interceptors property to include:
1.) format for adding 1 or many interceptors (using ", ")
2.) description of two currently available interceptors (InVMRegistryInterceptor and CachingRegistryInterceptor)
3.) description of when it would make sense or not make sense to use these two interceptors
Thanks!
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 8 months
[JBoss JIRA] Created: (JBESB-2882) Add support for fireUntilHalt to BusinessRulesProcessor
by Jeff DeLong (JIRA)
Add support for fireUntilHalt to BusinessRulesProcessor
-------------------------------------------------------
Key: JBESB-2882
URL: https://jira.jboss.org/jira/browse/JBESB-2882
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 4.6
Reporter: Jeff DeLong
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/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 9 months
[JBoss JIRA] Created: (JBESB-2830) Add Stream Mode support to BusinessRulesProcessor
by Jeff DeLong (JIRA)
Add Stream Mode support to BusinessRulesProcessor
-------------------------------------------------
Key: JBESB-2830
URL: https://jira.jboss.org/jira/browse/JBESB-2830
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Jeff DeLong
The BusinessRulesProcessor should support configuration for "StreamMode" with StatelessKnowledgeSessions. Most CEP applications will require StreamMode to enable sliding window support, garbage collection of expired facts, etc. This is really important (a necessity), and is turned on through the API.
This would require configuration such as
<action class="org.jboss.soa.esb.actions.BusinessRulesProcessor" name="OrderCountHistory">
<property name="ruleSet" value="OrderCount.drl"/>
<property name="ruleReload" value="true"/>
<property name="stateful" value="true"/>
<property name="vventProcessingOption " value="STREAM"/>
The code to use this would be something like:
kconfig = KnowledgeBaseFactory.newKnowledgeBaseConfiguration();
kconfig.setOption( EventProcessingOption.STREAM );
kbase = readKnowledgeBase(kconfig);
sconfig = KnowledgeBaseFactory.newKnowledgeSessionConfiguration();
sconfig.setOption( ClockTypeOption.get( ClockType.REALTIME_CLOCK.getId() ) );
ksession = kbase.newStatefulKnowledgeSession(sconfig, null);
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 9 months