Its not much of an extra step, and then you are not constrained to use
the methods only on the server. A client may also want to construct
resolved and relative URIs.
UriBuilder.fromUri(uriInfo.getBaseURI()).relativize(uri);
You may also be relativizing/resolving often from a uri template:
UriBuilder.fromResource(resourceClass).path(resourceClass,
"getCustomers").resolve(uri, "12345");
On 1/30/2013 8:39 AM, Marek Potociar wrote:
> IIRC, it's was a matter of the extra step required. UriInfo has enough information to be able to relativize any URI wrt. request URI. Which is what you essentially always want to do when sending back relative links.
>
> Marek
>
> On Jan 30, 2013, at 1:40 PM, Bill Burke <bburke_at_redhat.com> wrote:
>
>> Why aren't the relativize and resolve methods in UriBuilder?
>>
>> On 1/30/2013 5:41 AM, Marek Potociar wrote:
>>> Taking back my comment - I'm sorry, I misread the original request. I thought we're talking about resolveTemplate() methods.
>>>
>>> Marek
>>>
>>> On Jan 30, 2013, at 11:23 AM, Marek Potociar <marek.potociar_at_oracle.com> wrote:
>>>
>>>> We need those to align with WebTarget and to support some of its methods. We also discussed this IIRC.
>>>>
>>>> I'm strongly against removing the methods.
>>>>
>>>> Marek
>>>>
>>>> On Jan 28, 2013, at 11:49 PM, Bill Burke <bburke_at_redhat.com> wrote:
>>>>
>>>>> relatives and resolve. I don't seem to recall us discussing this.
>>>>>
>>>>> -1 for these new methods. We don't need to pollute the API with esoteric use cases.
>>>>>
>>>>> --
>>>>> Bill Burke
>>>>> JBoss, a division of Red Hat
>>>>> http://bill.burkecentral.com
>>>>
>>>
>>
>> --
>> Bill Burke
>> JBoss, a division of Red Hat
>> http://bill.burkecentral.com
>
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com