[jbosstools-issues] [JBoss JIRA] Updated: (JBIDE-6614) [ESB Editor] Support new ESB 4.9 Complex Event Processing functionality

[ https://jira.jboss.org/browse/JBIDE-6614?page=com.atlassian.jira.plugin.s... ] Brian Fitzpatrick updated JBIDE-6614: ------------------------------------- Original Estimate: 0 minutes Remaining Estimate: 0 minutes Assignee: Viacheslav Kabanovich (was: Brian Fitzpatrick) Fix Version/s: 3.2.0.Beta (was: 3.2.x) Slava, more new functionality from ESB 4.7 (see JBIDE-6615 and JBIDE-6616 for others)... Documentation has been added as additional configuration parameter descriptions for the BusinessRulesProcessor in the Services Guide here: http://docs.jboss.org/jbossesb/docs/4.9/manuals/pdf/Services_Guide.pdf Section 2.2.4 has an example of using the Complex Event Processing (CEP) properties in the context of the BusinessRulesProcessor configuration in an ESB config file. There's a list of BusinessRulesProcessor Action Configuration Properties in the section. Looks like new properties are (from JBESB-2883, JBESB-2882, JBESB-2830) : ruleAuditType=CONSOLE, FILE, THREADED_FILE ruleAuditFile=<filepath> ruleAuditInterval=<milliseconds> ruleFireMethod=FIRE_ALL_RULES or FIRE_UNTIL_HALT ruleEventProcessingType=CLOUD or STREAM ruleClockType=REALTIME or PSEUDO Looks like Channel may be new (JBESB-2831 and in section 2.2.6 of Services Guide) <property name="channels"> <!-- chan1 and chan2 are equivalent (but timeout only applies if async == false) --> <send-to channel-name="chan1" service-category="cat1" service-name="svc1" /> <send-to channel-name="chan2" channel-class="org.jboss.soa.esb.services.rules.ServiceChannel" service-category="cat1" service-name="svc1" async="true" timeout="30000" set-payload-location="org.jboss.soa.esb.message.defaultEntry" /> <!-- a custom channel --> <send-to channel-name="chan3" channel-class="com.example.MyChannel" /> </property> Hopefully you have enough info here. If not, we can always ask David Ward, who implemented these changes. -- 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