Sergey,
Backward compatibility for JAX-RS 1.X applications is very important. So adding new methods and new types should be fine, in general. As an example, we looked at Request and Response from JAX-RS 1.X and decided it was too difficult to change these types to accommodate the new requirements, so we opted for the introduction of HttpRequest and HttpResponse instead.
I suspect that we want to look at UriBuilder in the context of hyperlinking. But, if a form of declarative hyperlinking is agreed upon, I'm guessing there's probably less of a need to change UriBuilder. Right?
-- Santiago
On Jul 8, 2011, at 12:07 PM, Sergey Beryozkin wrote:
> We've seen some users asking reasonable questions about UriBuilder/etc
> being enhanced slightly, etc, so I'm asking if we can afford modifying
> existing constructs. 2.0 is a major release so I guess it could be an
> opportunity, but I'd like to get a clear picture first before coming up
> with proposals
>
> Sergey
>
> Guilherme Silveira wrote:
>> Would be really nice to just support and be able to construct something
>> new...
>>
>> Guilherme Silveira
>>
>>> 2011. 7. 8. 오후 12:57에 "Sergey Beryozkin" <sberyozkin_at_talend.com
>>> <mailto:sberyozkin_at_talend.com>>님이 작성:
>>>
>>> Hi
>>>
>>> What are JAX-RS 2.0 guarantees about running JAX-RS applications
>>> written against JAX-RS 1.1 ?
>>>
>>> How far can JAX-RS 2.0 go in updating existing constructs such as
>>> UriBuilder, etc ?
>>>
>>> Sergey
>>>
>
> --
> Sergey Beryozkin
>
> http://sberyozkin.blogspot.com
> Talend - http://www.talend.com
>
>