- December 26, 2012

We are happy to release two new versions of the Restlet Framework today. After a rather lengthy 2.1 release cycle due to the writing of the ‘Restlet in Action’ book, we want 2.2 development to last one year, with a release planned in summer 2013. See our detailed roadmap.

Stable 2.1 branch

We first released version 2.1.1 which fixes a dozen of bugs and marks the “2.1” branch as the new stable branch. As a result, the “2.0” branch has now reached its end of life, after about two years of maintenance since the release of 2.0.0. New releases will only be made if critical security bugs are found or for customers with professional support plans.

We now encourage everyone to migrate to version 2.1.1 for their Restlet applications in production, which should be easy from 2.0. See our migration guide for help on that front.

The internal HTTP connector has received several fixes and improvements, but we don’t consider it ready for heavy productions yet. We will keep improving its stability and scalability in the future 2.1.x revisions.

Testing 2.2 branch

The first major change is that the minimum requirement are now Java SE/EE 6 (including Servlet 3.0) . As a result, we were able to upgrade our Jetty extension to use version 8.1 of Jetty.

We no longer support Java 5 which has been the case since Restlet Framework version 1.0. If you still need to support Java 5 due to other requirements, we encourage you to keep using Restlet Framework 2.1.


Today, modern web API rely on OAuth 2.0 to secure access, providing revokable and delegable authorization. It is key for the Restlet Framework to fully support this standard on both the client and server sides.

With this first 2.2 milestone, the OAuth 2.0 extension has been upgraded to OAuth 2.0 draft 30 level. We still have a lot of work ahead to both fully support the final 2.0 version of the specification (RFC 6749), both on client and server side, and to update the documentation (Javadocs and user guide).


As this point, this extension is still considered experimental and we are looking for additional testers and contributors.

In addition, here are additional changes available:

  • HTTP PATCH method (RFC 5789) is now supported by default via Method.PATCH constant and @Patch annotation
  • JAX-RS extension has been enhanced to add client-side support based on JAX-RS annotations
  • Jackson extension has added support for the JSON binary (Smile), XML, YAML and CSV formats
  • OSGi extension has an OBAP pseudo-protocol (OSGi Bundle Access Protocol) client connector to allow access to resources from other OSGi bundles.
    • URI scheme: “obap://{bundleSymbolicName}/{pathToResource}”

Recent contributors

  • Andy Dennie
  • Brian Sletten
  • Dennis Mitchell
  • Emmanuel Liossis
  • Emanuele Ziglioli
  • Florian Bucklers
  • Grzegorz Godlewski
  • Jeff Plourde
  • Laurent Rustuel
  • Martin Grohmann
  • Nicolas Rinaudo
  • Shaun Elliott
  • Shotaro Uchida
  • Tim Peierls
  • Wei Wei Wang

Thanks to all others who helped us in various ways.

Additional resources

Changes log:

Download links: