[
https://jira.jboss.org/jira/browse/JBESB-2273?page=com.atlassian.jira.plu...
]
Kevin Conner updated JBESB-2273:
--------------------------------
Priority: Optional (was: Major)
Marking this as optional for now, as it is not scheduled for the platform release. We
should still aim to include this into the 4.6 release.
Extend BusinessRulesProcessor action to support entry-point
-----------------------------------------------------------
Key: JBESB-2273
URL:
https://jira.jboss.org/jira/browse/JBESB-2273
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Process flow
Affects Versions: 4.4 CP1
Reporter: Burr Sutter
Priority: Optional
Fix For: 4.6
BusinessRulesProcessor allows for a "stateful" rules session as of ESB 4.4,
however, it doesn't allow subsequent inbound messages to inject those messages into
the already existing stateful rules session via the entry-point API.
<action
class="org.jboss.soa.esb.actions.BusinessRulesProcessor"
name="OrderDiscountBasedOnCustomerHistory">
<property name="ruleSet"
value="OrderDiscountOnMultipleOrders.drl" />
<property name="ruleReload" value="false" />
<property name="stateful" value="true" />
<property name="object-paths">
<object-path esb="body.TheOrderHeader" />
<object-path esb="body.TheCustomer" />
</property>
</action>
We might extend this like so:
<object-path esb="body.TheOrderHeader" entry-point="OrderStream"
/>
<object-path esb="body.TheCustomer" entry-point="CustomerStream"
/>
The date time stamp should be based on message DOB but perhaps overrideable here as
well.
The use of entry-points would also mean that the Rules session is "self
cleaning" as it automatically garbage collects stale facts.
--
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