| Summary: | BusinessRulesProcessor action needs better support for stateful CEP scenarios | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 5 | Reporter: | Michael Pellegrini <mpellegr> | ||||||
| Component: | JBossESB | Assignee: | Nobody <nobody> | ||||||
| Status: | MODIFIED --- | QA Contact: | |||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | high | ||||||||
| Version: | 5.2.0.ER4 | CC: | kejohnso, kevin.conner, ldimaggi, tcunning | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | 5.2.0 GA | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| URL: | http://jira.jboss.org/jira/browse/SOA-3417 | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | Type: | Bug | |||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Bug Depends On: | |||||||||
| Bug Blocks: | 782575 | ||||||||
| Attachments: |
|
||||||||
|
Description
Michael Pellegrini
2011-09-26 13:18:43 UTC
Changing this at this point would have too big of an impact. It is possible to use CEP, without referencing DISPOSE/CONTINUE, by defining the "org.jboss.soa.esb.services.rules.continueState" property within jbossesb-properties.xml as "true". This will affect all references of stateful sessions as there is currently no way to specify this per action. I was aware of this option, and as you point out it could be too global of a setting in certain scenarios. I still think it would be best to keep this setting as part of the jboss-esb.xml at the BRP action (or even a new CEP action). For now, I worked around this using a custom action which controls the dispose/continue options based on receiving the first message or subsequent messages. Attached diff which enables default continue behaviour per action Attachment: Added: cep_diff Attachment: Added: test-cep-esb.zip Link: Added: This issue relates to JBESB-3698 Committed Kevin's patch to ESB, will be in ER5. cunningts-imac:product cunningt$ svn commit Sending product/samples/quickstarts/business_ruleservice_cep/readme.txt Sending product/services/jbrules/src/main/java/org/jboss/internal/soa/esb/services/rules/RuleInfoBuilder.java Sending product/services/jbrules/src/main/java/org/jboss/internal/soa/esb/services/rules/RuleInfoImpl.java Sending product/services/jbrules/src/main/java/org/jboss/internal/soa/esb/services/rules/RuleServiceCallHelper.java Sending product/services/jbrules/src/main/java/org/jboss/internal/soa/esb/services/rules/StatefulRuleInfoImpl.java Sending product/services/jbrules/src/main/java/org/jboss/soa/esb/actions/BusinessRulesProcessor.java Sending product/services/jbrules/src/main/java/org/jboss/soa/esb/services/rules/RuleInfo.java Sending product/services/jbrules/src/main/java/org/jboss/soa/esb/services/rules/RuleServicePropertiesNames.java Sending product/services/jbrules/src/test/java/org/jboss/soa/esb/actions/BusinessRulesProcessorUnitTest.java Transmitting file data ......... Committed revision 37516. cunningts-imac:product cunningt$ |