Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Tue, 11 Nov 2014 23:05:34 +0000 (UTC)
From: "clebert suconic (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: <JIRA.12753363.1415269222000.474251.1415747134066@Atlassian.JIRA>
In-Reply-To: <JIRA.12753363.1415269222000@Atlassian.JIRA>
References: <JIRA.12753363.1415269222000@Atlassian.JIRA>
 <JIRA.12753363.1415269222812@arcas>
Subject: [jira] [Commented] (ACTIVEMQ6-17) Add Broker Interceptor - like the
 Camel Broker Component in ActiveMQ 5
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/ACTIVEMQ6-17?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14207294#comment-14207294 ] 

clebert suconic commented on ACTIVEMQ6-17:
------------------------------------------

HornetQ already has that support on core protocol.

It's not at message level... so this wouldn't work for messages sent from AMQP, OpenWire or any other protocol. So, there's definitely space for improvement here.


> Add Broker Interceptor - like the Camel Broker Component in ActiveMQ 5
> ----------------------------------------------------------------------
>
>                 Key: ACTIVEMQ6-17
>                 URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-17
>             Project: Apache ActiveMQ 6
>          Issue Type: Bug
>            Reporter: Rob Davies
>
> One of the main reasons ActiveMQ is popular is its flexibility. Allowing Camel to intercept messages inside the broker (Camel Broker Component) - will allow some of the current BrokerPlugins (like TimeStamp) - to be implemented using Camel routes.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)