Hi
Hi,
That probably explains why my test for this with the 2.2-SNAPSHOT still
fails. The snapshot available from
http://people.apache.org/repo/m2-snapshot-repository/org/apache/cxf/apache-cxf/2.2-SNAPSHOT/
is from 17.10.2008. Any idea when a new snapshot is built?
What is the release schedule for 2.1.3 or is the current snapshot stable
enough for production?
Just discovered this email in my inbox :-) 2.1.3 has already been released - and I don't rememebr now if this fix (for dealing with
encoded URLs has made it 2.1.3 or not) but 2.1.4 will be coming shortly too.
Dan Kulp should know exactly when it will happen
Sorry for a very late response ...
Cheers, Sergey
Br,
Lasse
Sergey Beryozkin-3 wrote:
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)
--
View this message in context:
http://www.nabble.com/URL-escaping-%2B-tp20090011p20108771.html
Sent from the cxf-user mailing list archive at Nabble.com.
