[esb-issues] [JBoss JIRA] (JBESB-3786) Enable configuration and propagation of the JMS priority through the ESB aware services
[
https://issues.jboss.org/browse/JBESB-3786?page=com.atlassian.jira.plugin...
]
Kevin Conner closed JBESB-3786.
-------------------------------
Resolution: Done
The gateways now support the specification of the message flow priority using properties.
The property can be added in listener/bus/provider areas with the exception of the
CamelGateway (JBESB-3805) and EBWS (specified in the service).
Configuration is enabled by adding the property
<property name="messageFlowPriority" value="X"/> where X is a
number from 0 to 9 inclusive.
The list of gateways are
- scheduled (including file etc)
- groovy
- jms
- sql
- JCA inflow
- Camel (subject to above bug)
- Hibernate
- Http
- JBoss Remoting
- UDP
- EBWS
For EBWS the property must be specified within the "service" element.
Enable configuration and propagation of the JMS priority through the
ESB aware services
---------------------------------------------------------------------------------------
Key: JBESB-3786
URL: https://issues.jboss.org/browse/JBESB-3786
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Transports
Affects Versions: 4.11
Reporter: Kevin Conner
Assignee: Kevin Conner
The feature request is to have a priority configured on a gateway and then have that
propagate through the ESB services which are invoked as a result.
The priority should be applied to any JMS transports which are used to communicate with
ESB services, using the JMS message setJMSPriorty, and propagated through those services
to subsequent ESB service invocations.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira