On 08/11/11 13:24, Marek Potociar wrote:
> While entering slightly late this discussion, let me provide a summary of my take based on the feedback I read so far:
>
> IMHO:
>
> - for the reasons already argued, we need to be flexible about the API we provide in this space. Therefore I lean
> towards a programmatic API that may serve as the base support.
>
> - if we can reach an agreement, we may want to provide a few annotations, that may help to provide user convenience in
> the most typical use case scenarios. These annotations should be "mappeable" to the programmatic API. By which I mean to
> say that albeit not explicitly formulated by the spec, it should be clear that any new annotation would be substitutable
> by a piece of code using the programmatic API.
>
> - perhaps it is my misunderstanding, but I don't agree that JAX-RS resource classes should be tied to resource entities.
> Perhaps it was an unfortunate choice of the name, but JAX-RS resource classes are conceptually controllers, not models.
>
Yep, though the examples (elsewhere) which show JAXB beans acting as
subresources/etc may be contributing to some confusion, but agreed with
the last statement
Cheers, Sergey
> Marek
>
> On 11/01/2011 06:51 PM, Santiago Pericas-Geertsen wrote:
>> Hello Expert,
>>
>> The following wiki page [1] contains some ideas that build on the existing hypermedia support, making it a lot more
>> useful. Please provide feedback.
>>
>> The server part is based around a new method Link.fromResourceMethod(Class<?>, String). The client part simply provides
>> some minor extensions to take advantage of the extended meta-data. The example uses relative links for convenience; if
>> possible, let's delay the discussion on relative links for a separate e-mail thread.
>>
>> -- Santiago
>>
>> [1] http://java.net/projects/jax-rs-spec/pages/HypermediaExample
--
Sergey Beryozkin
http://sberyozkin.blogspot.com
Talend - http://www.talend.com