On Jan 13, 2010, at 12:37 PM, Felipe Gaścho wrote:
> one detail (within many others :) :
>
> Santiago is focusing on WADL, a controversial approach since the REST
> community reject the need of any external contract for REST style
> architecure. I know that even the smart guys over there become a bit
> religious sometimes, but I would vote to focus on the annotations
> instead of WADL based HATEOAS...
>
WADL is one area of focus.
Contrary to what some people have said it can be used for hypermedia
and used to generate proxies. It just depends on what proxies you
generate. Resource proxies will break some REST constraints. But, if
you can generate proxies for media types and link types from WADL then
such proxies are appropriate for machine-based hypermedia communication.
> more precisely I would like to see the next states
> (@ContextualActionSet) extracted automatically instead of manually
> coded.. (or customizable)....
>
How to you propose to automatically generate the state transitions
without the application defining what those transitions are?
The contextual action set defines the state transitions, what
transitions are allowable and thus, depending on the current state,
what hypermedia links will be present in a representation or link
headers. Such transitions are very much part of the application.
> It is very nice to see Jersey moving toward a 100% REST ready
> framework.. but hypermedia is still a sharp thing...
>
> let's see...
>
> in few days I will present Jresey at Jfokus, speaking briefly about
> REST as well.. I hope to hit the best target over there.. and bring
> back in the luggage a set of new ideas :)
>
> * that's why I am so quiet here :) damn slides to prepare :)
>
OK! Good luck.
Paul.