[JBoss JIRA] Created: (JBESB-3553) Provide option for Business Rules Processor Stateful Service to only dispose upon re-deployment
by Jeff DeLong (JIRA)
Provide option for Business Rules Processor Stateful Service to only dispose upon re-deployment
-----------------------------------------------------------------------------------------------
Key: JBESB-3553
URL: https://issues.jboss.org/browse/JBESB-3553
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Content Based Routing
Reporter: Jeff DeLong
The current support for Stateful Session in the Business Rules Processor uses Message Properties (continue and dispose) to determine when to create, use, or dispose the StatefulSession. This provides flexibility for Stateful Sessions usage, however at the cost of complexity (the setting of the Message Properties). A simpler approach would be to create the Stateful Session at service deployment time and dispose of it when the service is undeployed. With this approach the Message Properties would not need to be set. It it desirable to support this approach in addition to the current approach. It would be simpler to use, and cover many use cases (for example CEP use cases where memory management is performed by the engine and there is no requirement to dispose of the Stateful Session).
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] Created: (JBESB-3552) Provide alternative WS transport for jUDDI clients
by Kevin Conner (JIRA)
Provide alternative WS transport for jUDDI clients
--------------------------------------------------
Key: JBESB-3552
URL: https://issues.jboss.org/browse/JBESB-3552
Project: JBoss ESB
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Registry and Repository
Affects Versions: 4.9
Reporter: Kevin Conner
Assignee: Kevin Conner
Priority: Blocker
Fix For: 4.9 CP1
The juddi JAXWSTransport class creates a service using the port name, however there seems to be some confusion around the correct UDDI v3 service names as other implementers use different service names.
This should have been addressed in the next juddi release but will not be included in time for 4.9CP1. We need to provide an alternative transport until this happens.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months