Hi,
I just committed an update to the test, it works ok. Note, the actual snapshot jar containing the fix may not have been produced
yet, I commited the fix yesterday. That said, I'm not sure why it does not work with say CXF 2.1.3. Before the fix, we worked in a
'decoded' space, and it was a problem for requests like /foo/bar/http://baz.com, as the defaut template reg expression is ([^/]+?).
Requests like /bar=A%2BB will be decoded (in 2.1.3) to /bar=A+B and the above
reg expression should capture A+B.
But anyway, this looks to be all working fine in the latest snapshots (I didn't commit to 2.1.4-SNAPSHOT yet as I can't compile it
at the moment due to some maven problems)
Cheers, Sergey
It is almost like you wrote except that we only get the param value.
Example:
@Path("/foo")
class Foo {
@GET
@Path("/bar={bar}")
someMethod(@PathParam("bar") String bar) { ... }
}
I will run my code with 2.2-SNAPSHOT and check if we have this problem with
it.
Sergey Beryozkin-3 wrote:
Just wouild like to clarify that this is a sample request URI :
/foo/bar=A%2BB
can you please tell me how are you retrieving the bar value ?
is it like this :
@Path("/foo/{barPair}")
someMethod(@PathParam("barPair") String bar)
--
View this message in context:
http://www.nabble.com/URL-escaping-%2B-tp20090011p20104827.html
Sent from the cxf-user mailing list archive at Nabble.com.
