Hi

I'm not sure what a generic HATEOAS framework can do.
The number of possibilities is unlimited:
- have custom links, relative or absolute ones - as attributes or child nodes
- have Atom feeds/entries with atom:links
- have HTTP Link headers
- return WADL describing the resource tree

I'm not sure it is really generalizable.
I think though you can have done all of the above with CXF.

Simplifying dealing with links and generating them is interesting.
Capturing links in UI tools (modelling tools, EMF, UML, etec, etc) is
interesting

thanks, Sergey


On Thu, Apr 28, 2011 at 9:47 PM, Ivan Vitoria Sanchez
<[email protected]> wrote:
> I agree with David. In fact, I've built a JAX-RS Server with Spring and one 
> of my services return some "Feeds", which are based on HATEOAS strategy. The 
> "Feed" is a simple POJO marshaled with JAXB.
>
> Cheers,
>
> Ivan
>
> Ivan Vitoria Sanchez ([email protected])
> Grupo ICA; Informática y Comunicaciones Avanzadas S.L.
>
> Complejo Empresarial Ecourban
> Edificio Azul
> Planta 3ª Oficina 4ª
> C/Almogàvers 119-123
> 08018 Barcelona
>
> Telf. 93.452.02.65
> Fax. 93.451.35.42
>
> https://www.grupoica.com
>
>
>
> -----Mensaje original-----
> De: KARR, DAVID (ATTSI) [mailto:[email protected]]
> Enviado el: jue 28/04/2011 21:51
> Para: [email protected]
> Asunto: RE: CXF with HATEOS or hypermedia
>
>> -----Original Message-----
>> From: cogitate [mailto:[email protected]]
>> Sent: Thursday, April 28, 2011 10:43 AM
>> To: [email protected]
>> Subject: CXF with HATEOS or hypermedia
>>
>> We are fully invested in CXF for supporting payloads of various types -
>> not
>> just Webservices but also RESTful services. However , for RESTful
>> services
>> we want to have "hypermedia" support.
>>
>> Currently it seems CXF isn't supporting this and we are under pressure
>> to go
>> to "Jersey" - however, i wouldn't want to throw our CXF code out.
>>
>> what's the way out?
>> design principles or information on any future support for Hypermedia
>> would
>> be appreciated.
>
> HATEOAS (not HATEOS) is a simple concept.  You don't need Jersey to use 
> HATEOAS.  If you use the UriBuilder you can construct URLs that point to 
> controller methods.  You can then populate responses with that data.
>
> Jersey may provide more complete features (I've been seeing something about 
> "linking"), but HATEOAS is what you make of it.
>
>
>
>



-- 
Sergey Beryozkin

Application Integration Division of Talend
http://sberyozkin.blogspot.com

Reply via email to