Return-Path: X-Original-To: apmail-camel-issues-archive@minotaur.apache.org Delivered-To: apmail-camel-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 07936D7D9 for ; Sat, 22 Sep 2012 06:17:16 +0000 (UTC) Received: (qmail 89879 invoked by uid 500); 22 Sep 2012 06:17:15 -0000 Delivered-To: apmail-camel-issues-archive@camel.apache.org Received: (qmail 89734 invoked by uid 500); 22 Sep 2012 06:17:11 -0000 Mailing-List: contact issues-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@camel.apache.org Delivered-To: mailing list issues@camel.apache.org Received: (qmail 89392 invoked by uid 99); 22 Sep 2012 06:17:08 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 22 Sep 2012 06:17:08 +0000 Date: Sat, 22 Sep 2012 17:17:08 +1100 (NCT) From: "Claus Ibsen (JIRA)" To: issues@camel.apache.org Message-ID: <1000205858.110655.1348294628169.JavaMail.jiratomcat@arcas> In-Reply-To: <1028802457.110003.1348267567781.JavaMail.jiratomcat@arcas> Subject: [jira] [Commented] (CAMEL-5637) Tracking/Waypoint Slip intercept strategy MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CAMEL-5637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13461036#comment-13461036 ] Claus Ibsen commented on CAMEL-5637: ------------------------------------ Raul, there is already support and logic for this. eg hence why the Camel tracer can do what it does. Its the message history EIP pattern http://www.eaipatterns.com/MessageHistory.html Its currently tied to UoW where you can get the trace nodes. For Camel 3.0 we have on the roadmap to refactor this logic, and introduce a better end user API for that as well. http://camel.apache.org/camel-30-roadmap.html So IMHO dont introduce a new layer of code when there is already existing. > Tracking/Waypoint Slip intercept strategy > ----------------------------------------- > > Key: CAMEL-5637 > URL: https://issues.apache.org/jira/browse/CAMEL-5637 > Project: Camel > Issue Type: New Feature > Components: camel-core > Reporter: Raul Kripalani > Assignee: Raul Kripalani > Priority: Minor > Fix For: 2.11.0 > > > In a modular middleware system, an Exchange will frequently traverse a number of routes and Camel contexts during its processing. > A Tracking Slip or Waypoint Slip is a special Camel property that keeps track of all the places where the Exchange has been. > Envisioned as an InterceptStrategy, it will act as an InterceptFrom construct that adds the ID of the current route, the ID of the Camel context or both (configurable) into a List inside a property called {{CamelTrackingSlip}} or {{CamelWaypointSlip}}. > It will aid debugging, Business Activity Monitoring, data mining, log mining and what not. By using the {{log:}} endpoint with {{showProperties=true}}, this property will be printed to log files. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira