I am pleased to announce the first GA release of JBoss RESTEasy. All documentation and download links are available at RESTEasy's JBoss.org project page. JBoss RESTEasy is a framework that allows you to write RESTFul Web Services in Java. It is a fully certified and portable implementation of JAX-RS specification. JAX-RS is a new JCP specification that provides a Java API for RESTful Web Services over the HTTP protocol. RESTEasy can run in any Servlet container, but tighter integration with the JBoss Application Server is also available to make the user experience nicer in that environment. While JAX-RS is only a server-side specification, RESTEasy has innovated to bring JAX-RS to the client through the RESTEasy JAX-RS Client Framework. This client-side framework allows you to map outgoing HTTP requests to remote servers using JAX-RS annotations and interface proxies. Features * Fully certified JAX-RS implementation * Portable to any app-server/Tomcat that runs on JDK 5 or higher * Embeddedable server implementation for junit testing * Rich set of providers for: XML, JSON, YAML, Fastinfoset, Atom, etc. * JAXB marshalling into XML, JSON, Fastinfoset, and Atom as well as wrappers for arrays, lists, and sets of JAXB Objects. * Asynchronous HTTP (Comet) abstractions for JBoss Web, Tomcat 6, and Servlet 3.0 * EJB, Spring, and Spring MVC integration * Client framework that leverages JAX-RS annotations so that you can write HTTP clients easily (JAX-RS only defines server bindings) Special thanks goes to all our independent contributors, specifically: Solomon Duskis, Ryan McDonough, Olivier Brand, Martin Algesten, Michael Brackx, and Justin Edelson.

Thanks for 'allowing' us to do this. What would we do without you?

Thanks for 'allowing' us to do this. What would we do without you?

Elementary my dear Watson. You would have to use Rails... or a Sun product.

Any comparisons to Jersey?

Any comparisons to Jersey?

I chose to use (and then contribute to RESTEasy) because of the Spring integration and the slick RESTEasy RESTful client. RESTEasy's Spring integration is more natural than Jersey's SPring integration. RESTEasy's client performs the grunt work based on a proxy to a Java interface which has JAX-RS annotations. Jersey does have some features that RESTEasy doesn't, like GZip and interceptors. Jersey also probably has more adoption, but that's just conjecture.

Any comparisons to Jersey?

I chose to use (and then contribute to RESTEasy) because of the Spring integration and the slick RESTEasy RESTful client. RESTEasy's Spring integration is more natural than Jersey's SPring integration. RESTEasy's client performs the grunt work based on a proxy to a Java interface which has JAX-RS annotations.

Jersey does have some features that RESTEasy doesn't, like GZip and interceptors. Jersey also probably has more adoption, but that's just conjecture.

>RESTEasy does support GZIP - see JBOSS doc and my comments on JAXB-JSON Sample code.

-Francois

It would be interesting to learn what features people would like us to focus on. Currently we're diving into: * interception at various points in request/response flow * gzip * Client side caching for the client framework (think of what your browser does) * Server side caching (think of what squid does) * Seam integration (really updating the old stuff) * Web Beans integration * JBoss 5 integration (from a deployment perspective) Some people want WADL but I'm not sure if its something I want to even push in the Java REST community. We may do a little more Spring integration, but I think we've nailed that pretty well. -- Bill Burke JBoss, a division of Red Hat http://bill.burkecentral.com

Could we get comet for jetty 6?

Could we get comet for jetty 6?

Jetty continuations are just bizarre. Using exceptions for control flow? Very very bad, IMO. Plus I am very reluctant to re-engineer RESTEasy to support control-flow using exceptions especially when Servlet 3.0 is going to make Jetty 6 very legacy.