Hi Jason Providing a proxy-based RESTful client api may be regarded as a controversial step given there's an opinion it does not really differ much from a soap-based client api. IMHO, it's more a matter of taste given that what happens on the wire after a proxy does the invocation is very HTTP-centric and CXF can do a lot to ensure a proxy stays 'operational' as long as possible...Essentially, every REST resource has a uniform interface but every proxy has uniquely named methods, but it is only a client view (ex, proxy.getBook() vs webClient.get(Book.class)).
Proxy based api certainly helps users with trying to invoke against restful servers, ultimately a user can see if it's too restricting and if yes then just switch to a web client (in CXF you can do at runtime) FYI, RestEasy also provides a proxy-based api cheers, Sergey On Tue, Mar 16, 2010 at 8:32 PM, JasonAB <jaso...@acm.org> wrote: > > > > Sergey Beryozkin-5 wrote: > > > > I believe Jersey uses a ClientResponse class which may have a method like > > the one you mentioned but you'd need to have a signature returning a > > ClientResponse for a proxy method to work as you expect. > > > > Thanks very much for the help - that's about what I expected. It would be > great is CXF could be the leader in RESTful clients, as that seems to be > lacking across the board. > > jason > > -- > View this message in context: > http://old.nabble.com/JAX-RS-proxy-client-and-getEntity%28%29-tp27912567p27924102.html > Sent from the cxf-user mailing list archive at Nabble.com. > >
