Re: [Jersey] JAX-RS == REST? Or not? (was Re: [Jersey] What HATEOAS actually means)

From: Paul Sandoz <Paul.Sandoz_at_Sun.COM>
Date: Tue, 16 Feb 2010 09:50:10 +0100

Hi Kevin,

The Sun Cloud API is RESTful. Trust me :-)

We need to address your point about examples, with use-cases, when we
have more solid API details around hypertext and JAX-RS.

People are already developing hypertext applications using JAX-RS they
are just doing the work themselves. For example, Felipe is doing just
that (he a link on this list to some slides out recently). IIRC Marc,
and he can confirm or deny, has developed hypertext applications in
the identity space using JAX-RS, but i do not think those are public.
And i am sure others have developed similar examples.


On Feb 16, 2010, at 8:29 AM, Kevin Duffey wrote:

> > Hopefully we can clarify this further with more concrete examples.
> I hope soon.. I would really like to know the "right way" to build
> HATEOAS apis. :D
> I have read this extremely long thread, and am really really
> confused now as to what is what. I thought the Sun cloud APIs was a
> completely restful API design. However, this notion that the client
> maintains state has got me a bit confused now. I would love to see
> some truly RESTful examples using Jersey/JAX-RS.. how to implement
> for example HATEOAS in the present JAX-RS such that I can claim my
> API is truly RESTful and that everyone on this thread would agree on.