users@jersey.java.net

Re: [Jersey] Shouldn't Jersey decode _at_Path before matching the regex?

From: Marc Hadley <Marc.Hadley_at_Sun.COM>
Date: Mon, 05 Jan 2009 15:40:38 -0500

PMFJI

On Jan 5, 2009, at 2:06 PM, Gili wrote:
>
> 1) Do you decode the query/matrix arguments before passing it to the
> user? I assume so.
>
Decoding is on by default but can be disabled with @Encoded.

> 2) Is it legal to use @Path against multiple path segments at once?
> Such
> as @Path("first/second")
>
Yes

> Are there any other possible conflicts or is the '/'
> character the only
> one?
>
Any regex literal not in the RFC 3986 pchar production needs to be in
encoded form.

> 3) At the very least I would say that the @Path Javadoc should
> indicate
> near the top that regular expression are run against the encoded URI.
> The Javadoc for "value" is very "busy" so you would have to include
> this
> very early on so people don't scan past it.
>
You could apply that same logic to any of the details which would just
move the contents of the doc for value to the outer doc. I think it
makes most sense where it is since it refers to the regex production.

Marc.

---
Marc Hadley <marc.hadley at sun.com>
CTO Office, Sun Microsystems.