Yea, looks like so. I had a chance to look at this bug briefly, what happens is that by the time JAX-RS impl gets the control, it has a fully decoded URI already, like /books/Good/morning, so the decoding happens much earlier in the stack... I'll try to get to the bottom of it asap - I'm a bit overwhelmed with the other work though at the moment Cheers, Sergey
-----Original Message----- From: Tarjei Huse [mailto:[EMAIL PROTECTED] Sent: 14 October 2008 08:47 To: [email protected] Subject: Re: Slashes in request parameters for a JAX-RS service Sric wrote: > I have defined a jax-rs service that accepts a string value as one of the > path parameters using CXF 2.1. I have deployed this in Tomcat 5.5. I have > configured Tomcat so that it will accept encoded forward and back slash > arguments (ex: Good%5Cmorning). However when I try to submit a string with > either an encoded forward or backward slash, I always get an HTTP 500 error > with a service error stating - No operation matching request path exception > on server. CXF seems to interpret the 1 param as 2 request parameters - > Good/Morning in the example I mentioned earlier. Is it possible to configure > CXF to interpret the encoded slash as a part of a single string parameter. > Hi, I think you may have hit this bug: http://issues.apache.org/jira/browse/CXF-1820 I ended up using Jersey instead. Regards, Tarjei > Thanks > Sriram >
