Mailing-List: contact dev-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Received-SPF: pass (athena.apache.org: domain of freeman.fang@gmail.com
 designates 74.125.83.169 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:from:to:in-reply-to:content-type:mime-version:subject
         :date:references:x-mailer;
        b=fpnNv1T0DvcQIP4cEy40yuMistD6pRZf8DrDvXiBwLvZxd/+vgDBUwq6l/L2lLTNHI
         qlzoPGxKp9eLjIfNLMUQDFuNCjIUIB9wU0pxeYNzwYbeCuRK3cBNFlgHYkAN/Jkk2T/4
         hbfaj0HC6UFL+N8wjgKePlYhJoFRsZV1HGi5U=
Message-Id: <CF516D07-5390-4FFC-B598-FA943411E785@gmail.com>
From: Freeman Fang <freeman.fang@gmail.com>
To: dev@cxf.apache.org
In-Reply-To: <B4A8A44A-E1D3-49AB-92A9-BE2D6A92DEE2@lab49.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-4-965921420
Mime-Version: 1.0 (Apple Message framework v935.3)
Subject: Re: JMS Username/Password bug
Date: Wed, 18 May 2011 11:50:35 +0800
References: <B4A8A44A-E1D3-49AB-92A9-BE2D6A92DEE2@lab49.com>

--Apple-Mail-4-965921420
Content-Type: text/plain;
	charset=UTF-8;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: quoted-printable

Hi Chris,

Thanks for the patch, I've create  CXF-3532[1] to track this issue.
However I think the correct way is that you append the patch for this =20=

issue where you need "Grant License to ASF", you just need register to =20=

JIRA, could you do that?

[1]https://issues.apache.org/jira/browse/CXF-3532

Freeman
On 2011-5-18, at =E4=B8=8A=E5=8D=881:57, Christopher Pike wrote:

> Hi,
>
> I recently encountered a bug with the handling of usernames and =20
> passwords in JMS configuration.  The bug is that the connection =20
> username was being set as the password on a JMS endpoint.  The =20
> details of the problem I was encountering are here: =
http://cxf.547215.n5.nabble.com/JMS-Username-Password-issue-td4384709.html=

>
> I have taken the liberty of patching the bug, the patch file is =20
> attached.  I tried to follow the submission instructions and create =20=

> a JIRA item, but unfortunately I don't seem to have authority to =20
> create a JIRA item as an anonymous user.  You will also notice that =20=

> I have done some very mild refactoring to make the code a bit more =20
> testable and avoid sending messages and relying on the timing of =20
> sleep statements for the test to pass.
>
> Regards,
> Chris Pike
>
>
> This email and any attachments may contain information which is =20
> confidential and/or privileged. The information is intended =20
> exclusively for the addressee and the views expressed may not be =20
> official policy, but the personal views of the originator. If you =20
> are not the intended recipient, be aware that any disclosure, =20
> copying, distribution or use of the contents is prohibited. If you =20
> have received this email and any file transmitted with it in error, =20=

> please notify the sender by telephone or return email immediately =20
> and delete the material from your computer. Internet communications =20=

> are not secure and Lab49 is not responsible for their abuse by third =20=

> parties, nor for any alteration or corruption in transmission, nor =20
> for any damage or loss caused by any virus or other defect. Lab49 =20
> accepts no liability or responsibility arising out of or in any way =20=

> connected to this email.
> <patch.txt>

---------------------------------------------
Freeman Fang

FuseSource
Email:ffang@fusesource.com
Web: fusesource.com
Twitter: freemanfang
Blog: http://freemanfang.blogspot.com
Connect at CamelOne May 24-26
The Open Source Integration Conference


--Apple-Mail-4-965921420--