- December 10, 2014

Nine months after release 2.2, the whole Restlet team is proud to announce Restlet Framework 2.3 and our roadmap for 3.0 !

Besides keeping the framework editions and dependencies up-to-date this version vastly enhances the framework capabilities in terms of API documentation and management beyond its initial implementation and consumption focus.

This version is also the first to realize Restlet’s vision of a comprehensive web API platform, including Restlet Studio (a web IDE for APIs crafting), APISpark (the first PaaS for APIs) and Restlet Framework.

Framework whiteBg_high_res

Main changes

  • Web API documentationmanagement
    • introspection of code written with Restlet API and JAX-RS API
    • dynamic API description in Swagger 1.2 / 2.0 and RAML 0.8
    • firewall with rate limitation and security service
    • syncing API descriptors (see tutorial) introspected in APISpark
    • control of local agent (see tutorial) from APISpark
  • Java 7 requirement (performance, security, modern Javadocs)
  • Android 4, GAE 1.9 and GWT 2.7 compatibility
  • Jetty 9.2 upgrade adding an HTTP client and a SPDY server
  • CORS support (Cross-Origin Resource Sharing)
  • @Status annotation to map Java exceptions to HTTP errors
  • direct access to raw HTTP headers (getHeaders() method)


Majors contributors

Thanks to all the contributors who helped with the release:

  • Andrew Hughes
  • Claus Ibsen
  • Edouard Mercier
  • Emmanuel Liossis
  • Emanuele Massara
  • Graham Smith
  • Jack Jones
  • Jeremy Gustie
  • Jim Trainor
  • Koen Maes
  • Kristoffer Gronowski
  • Marcus NL
  • Robert Fischer
  • Roy Olsen
  • Tal Liron
  • Tim Peierls
  • Ralph van Etten
  • Tal Liron
  • Thomas Munz
  • Vishnu Perabathini


Roadmap for 3.0 version

Releasing a new major version is also the opportunity to  look forward. After a series of important by incremental releases in the 2.x branch, we thought it was time for deeper changes based on all the feed-back we received since version 2.0 released four years ago!

Here are the main topics we consider addressing in the next 3.0 version. Please share your thoughts with us.