Mailing-List: contact activemq-users-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: activemq-users@geronimo.apache.org
Received-SPF: pass (idunn.apache.osuosl.org: domain gmail.com designates
 66.249.82.225 as permitted sender)
DomainKey-Status: good
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=iU+T6xHFzGKbK9GbUcwootF61JMMykF8dzSsahB7H/xFL1Sdo5KW+N6ruxP0CmimYjkyChbWwGxJgpcnSUlhQ1O0ma/S2g2+X4vifrTE+SgnuYg1oRkt1JMCMmBhH1FBngD5cDFKbd4BlnwNQhuhk3UxZTlYX0OI43Cj29XJWRI=
Message-ID: <ec6e67fd0609250440m4678b443q42c8680ed8b46579@mail.gmail.com>
Date: Mon, 25 Sep 2006 12:40:26 +0100
From: "James Strachan" <james.strachan@gmail.com>
To: activemq-users@geronimo.apache.org
Subject: Re: Sender Name/ID
In-Reply-To: <653849d10609230949h7b762c9ax6c388152813f73a2@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <4789096.post@talk.nabble.com>
	 <ec6e67fd0606090327k23ffeef4rbf7348d110fba771@mail.gmail.com>
	 <653849d10609230949h7b762c9ax6c388152813f73a2@mail.gmail.com>

On 9/23/06, Kelly Campbell <kelly.a.campbell@gmail.com> wrote:
> Hi James, this JMSXUserID feature is great, however I had a few
> problems using it so I have a couple of questions and possible
> enhancements for the documentation.
>
> I first tried to use
> javax.jms.Message.getStringProperty("JMSXUserID"), but that always
> returned null, so I found out that I had to cast the message and use
> ActiveMQMessage.getUserId().

Hmm, thats strange - we've a test case called
JmsTopicSendReceiveWithEmbeddedBrokerAndUserIDTest which uses the
following code which works fine...

String userID = message.getStringProperty("JMSXUserID");

I wonder can you create a test case taht fails to return the JMSXUserID?


> Is that the intended usage or should you be able to get it via a
> property? If not, can we add something to the JMSXUserID web page that
> documents this with an example?

No it should work


> Also, I'll have a patch soon that fixes what looked like a problem
> with the userid never getting set in the broker. It's part of a larger
> patch which enhances the SSL security Sepand contributed last week.

Great. Note that currently the JMSXUserID header is only set i you
enable it on the BrokerService
via the populateJMSXUserID flag.

-- 

James
-------
http://radio.weblogs.com/0112098/