Yes, this method obviously won't work across domains. I have no idea what
will happen in practice if called with a cross domain URI, but it clearly
can't work as intended. If you're load balancing across multiple servers,
you should be able patch the URL as you proposed. You'll need to handle this
manually though, jersey can't help you.
2011/4/16 Gili <cowwoc_at_bbs.darktech.org>
> 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:
> http://java.net/jira/browse/JERSEY-708
>
> 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?
>
> Gili
>
> --
> View this message in context:
> http://jersey.576304.n2.nabble.com/Decoding-URI-into-path-parameters-tp6167750p6279068.html
> Sent from the Jersey mailing list archive at Nabble.com.
>