[
https://issues.jboss.org/browse/JBESB-3758?page=com.atlassian.jira.plugin...
]
Tom Cunningham resolved JBESB-3758.
-----------------------------------
Resolution: Done
Added org.jboss.internal.soa.esb.message.filter.ServiceRouteFilter, which can be
configured as a filter within jbossesb-properties.xml (see "filter" properties).
Once configured in jbossesb-properties.xml, it can be configured on either a service
or a message level, and it will add into the context logging that the service has started
or ended.
To configure it on a service level, add recordRoute="true" in your service
definition. To configure it on a message level, add a "service-record-route"
property to the message and set it to "true". You must configure one of
these two options to activate the service route recording.
RecordRoute functionality on both service and message basis
-----------------------------------------------------------
Key: JBESB-3758
URL:
https://issues.jboss.org/browse/JBESB-3758
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.11
Reporter: Tom Cunningham
Assignee: Tom Cunningham
Fix For: 4.11
Provide new, optional configuration options for ESB services to specify that the
message header should be updated upon service entry and service exit. This
allows users to track the history of the message through a set of services to see
what path it took. Reasonable default value to capture is the service name. This
is not intended to be a routing ticket.
Comments: A suggestion would be to include a 'record route' option for a service
and
message, placing the information within the message context. The information
should start with the originator (service, gateway, client) and add other services
as the message progresses. We already have the EntryExitTimeFilter and
GatewayFilters, I'm sure it would be easy to extend their functionality and link in
to the current service information.
--
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