[Jersey] Re: Decoding URI into path parameters

From: Gili <>
Date: Sat, 16 Apr 2011 07:51:44 -0700 (PDT)

Hi Daniel,

   Looks like exactly what I was asking for, except that it's not clear how
it will handle URIs pointing to a remote host so I filed a bug report:

   I propose it reject remote hosts because "John Smith" for my service
might be different than "John Smith" on someone else's service with
identical paths. Furthermore, if users wish to match foreign hosts (think
load-balancing), they can swap out the host component to the value returned
by UriInfo (or we can add a convenience method).

   What do you think?


View this message in context:
Sent from the Jersey mailing list archive at