Return-Path: X-Original-To: apmail-activemq-users-archive@www.apache.org Delivered-To: apmail-activemq-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BFD43F660 for ; Mon, 22 Apr 2013 13:57:09 +0000 (UTC) Received: (qmail 18725 invoked by uid 500); 22 Apr 2013 13:57:09 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 18680 invoked by uid 500); 22 Apr 2013 13:57:09 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Received: (qmail 18671 invoked by uid 99); 22 Apr 2013 13:57:09 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Apr 2013 13:57:09 +0000 X-ASF-Spam-Status: No, hits=2.8 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of christian.posta@gmail.com designates 209.85.217.180 as permitted sender) Received: from [209.85.217.180] (HELO mail-lb0-f180.google.com) (209.85.217.180) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Apr 2013 13:57:05 +0000 Received: by mail-lb0-f180.google.com with SMTP id t11so5649629lbi.39 for ; Mon, 22 Apr 2013 06:56:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=MWEAh6oewNqbyz9CHaOT6PNdLrJ1LRc0swA2njDK+aE=; b=FKAxQ5UHgfl08dwxg50Vbx87+LBknH0PluppDOS52odBgIRCHurEC4ifsy/h+ZVtoG 2mvoxZTAe/G/T8wlIij/zRLYh6j/LtkO42iSFkIk3LpqVJIMEdds4SdQ2gDUz8AAJzPI 2lkoaXTEeOop6tOtDpNh2K7TN7ig2e041B85lFPD8buBjhUiO4OEvfCdY9ZheGa0tpD/ WLXWp4mDEHVL1jtB+Y8dT2Q3wX44tkyAClLdvq2iD/yrapKaZ0vxIpQGma6ftvCi3k1c W3oUOVbAxZEBBum9tjdxbqVi+C7kRqIyxd0stSQaW7LZP09uIvWfsa9gU3ohZAyfszIT h4HQ== MIME-Version: 1.0 X-Received: by 10.112.129.202 with SMTP id ny10mr3585678lbb.124.1366639003884; Mon, 22 Apr 2013 06:56:43 -0700 (PDT) Received: by 10.114.96.194 with HTTP; Mon, 22 Apr 2013 06:56:43 -0700 (PDT) In-Reply-To: <1366637941192-4666115.post@n4.nabble.com> References: <1366637941192-4666115.post@n4.nabble.com> Date: Mon, 22 Apr 2013 06:56:43 -0700 Message-ID: Subject: Re: ActiveMQ MessageConsumed event From: Christian Posta To: "users@activemq.apache.org" Content-Type: multipart/alternative; boundary=047d7b3441d65ce4df04daf3708a X-Virus-Checked: Checked by ClamAV on apache.org --047d7b3441d65ce4df04daf3708a Content-Type: text/plain; charset=ISO-8859-1 Why not just use SSL? On Mon, Apr 22, 2013 at 6:39 AM, jonfrias wrote: > Hi all, > > I am writing because I'm implementing my own activemq-broker which > implements some feautures extra over the default version. > > I'm implementing the encryptation feature to all the messages which are > sent > within servicemix. To do this: > > 1 - I have overrided the method "preProcessDispatch". In this method I can > intercept the messages before they are sent and I encrypt the body of the > message. > > 2 - I need to intercept now the messages before they are consumed by the > consumers to decrypt the body of the messages. I have tried with these > methods: > * public void messageConsumed(ConnectionContext context,MessageReference > messageReference) > * public void messageDelivered(ConnectionContext context,MessageReference > messageReference) > > but none of them worked. I even try to write some text in the log to verify > if these methods are executed and apparently they are not. > > Can anybody tell me which method I should use? Or what am I doing wrong if > the methods I have tested are correct? > > Thanks a lot in advance. > > Best regards, > > Jon > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/ActiveMQ-MessageConsumed-event-tp4666115.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > -- *Christian Posta* http://www.christianposta.com/blog twitter: @christianposta --047d7b3441d65ce4df04daf3708a--