Description of problem: https://issues.jboss.org/browse/JBESB-3758 RecordRoute functionality on both service and message basis Fixed in ER1 - this bz is logged to track the fix and to ensure QE verifies Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Not ready yet, see https://bugzilla.redhat.com/show_bug.cgi?id=828778
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: A RecordRoute functionality has been added for messages and services. This places tracking information within the message context. It can be configured as a filter within jbossesb-properties.xml.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1 +1 @@ -A RecordRoute functionality has been added for messages and services. This places tracking information within the message context. It can be configured as a filter within jbossesb-properties.xml.+RecordRoute functionality has been added for messages and services. This places audit tracking information within the message context. Configure it as a filter within the jbossesb-properties.xml file.
Look like this should be fixed in ER4.