Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Received-SPF: pass (nike.apache.org: local policy includes SPF record at
 spf.trusted-forwarder.org)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: Upgrade to CXF 2.7.10
From: Daniel Kulp <dkulp@apache.org>
In-Reply-To: 
 <CALvzYd94fFXk6KCVx7Vc2NThXzHsmOYjUYAp=CCHvxvij9YNdw@mail.gmail.com>
Date: Mon, 10 Feb 2014 11:32:09 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <1E55964D-816D-4226-91E6-FF6B28855AF1@apache.org>
References: 
 <CALvzYd94fFXk6KCVx7Vc2NThXzHsmOYjUYAp=CCHvxvij9YNdw@mail.gmail.com>
To: dev@camel.apache.org


On Feb 10, 2014, at 2:43 AM, Christian M=FCller =
<christian.mueller@gmail.com> wrote:

> After upgrading to CXF 2.7.10 in camel-2.11.x,
>=20
> =
org.apache.camel.component.cxf.AbstractCXFGreeterRouterTest.testPublishEnd=
pointUrl
>=20
> is failing on my machine. I will have a look at it in the evening. If =
one
> of the CXF fellows could have a look at it before, I would appreciate =
it.
>=20
> I don't see this issue in master or camel-2.12.x which I also upgrade =
to
> CXF 2.7.10.

Fixed.  It=92s something that was not back ported from 2.12 to 2.11.   =
Done now.


HOWEVER, while debugging this, I noticed that the HTTP component or =
something is taking a url like:

http://localhost:8080/Foo?wsdl

and transforming it and then sending out:

/Foo?wsdl=3D

as the URL in the GET line on the request.   It=92s a little strange =
that the original URL isn=92t used as is.  Not a problem for CXF, but I =
wonder if it would be for other HTTP endpoints if they are processing =
the URL line themselves and not expecting the =3D.


--=20
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com