Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <493519FD.3030708@ttmsolutions.com>
Date: Tue, 02 Dec 2008 12:20:29 +0100
From: Dejan Bosanac <dejan.bosanac@ttmsolutions.com>
User-Agent: Thunderbird 2.0.0.17 (X11/20080925)
MIME-Version: 1.0
To: users@activemq.apache.org
Subject: Re: Disable Stomp transport from sending messages
References: <20774719.post@talk.nabble.com>
In-Reply-To: <20774719.post@talk.nabble.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Hi,

why don't you just use standard ActiveMQ security mechanism; connect
Stomp clients with the appropriate credentials and give read-only access
to destinations?

Cheers

-- 
Dejan Bosanac


http://www.ttmsolutions.com - get a free ActiveMQ user guide

ActiveMQ in Action - http://www.manning.com/snyder/
Scripting in Java - http://www.scriptinginjava.net


njones wrote:
> Hi.
>
> We have a case at work where we want to disable the sending of messages over
> the stomp transport. Is this possible?
>
> I was looking at a custom BrokerFilter that overrides the send method and
> checks the connection info, but in my tests the Connection is being stripped
> out of the message at some stage during sending. It's there when I create it
> but gets lost along the way.
>
> I'm using version 5.2
>
> Any help would be appreciated.
> Thanks
> Nick.
>