User guide
- Part 1 - Introduction
- Part 2 - Core Restlet
- Part 3 - Restlet Editions
  - Overview
  - Android
    - Overview
    - Sample
  - Google App Engine
  - Google Web Toolkit
    - Overview
    - Architecture
    - Deployment
    - Examples
    - JSON
    - Server code invocation
    - Setup
    - Tips
    - XML
  - Java EE
    - Overview
    - Client connectors
  - Java SE
    - Overview
    - Logging
  - OSGi
- Part 4 - Restlet Extensions
  - Overview
  - Editions matrix
  - Atom
  - Crypto
  - E4
  - EMF
  - FileUpload
  - FreeMarker
  - GAE
  - GSON
  - Guice
  - GWT
  - HTML
  - HTTP Client
  - JAAS
  - Jackson
  - JavaMail
  - JAXB
  - JAX-RS
  - JDBC
  - Jetty
  - JiBX
  - JSON
  - jSSLutils
  - Lucene
  - Nio
  - OAuth
  - OData
    - Overview
    - Tutorial
  - OpenID
  - OSGi
  - RAML
  - RDF
  - ROME
  - SDC
  - Servlet
  - Simple
  - SIP
  - SLF4J
  - Spring
    - Overview
    - Integration modes
    - Configuring Restlet beans
    - A complete example
    - Configuration of Restlet resources
  - Swagger
  - Thymeleaf
  - Velocity
  - WADL
  - XDB
    - Overview
    - Architecture - Introduction
    - Installing
    - Testing
    - FAQ
    - Future plans - Known caveats
    - XdbRepresentation
    - Introduction, download, compiling and installing
    - Running and testing
    - Implemented services
    - Todo List
  - XML
  - XStream
- Appendices
Tutorials
Javadocs
Change Log

Overview

The Restlet framework is composed of two main parts. First, there is the “Restlet API”, a neutral API supporting the concepts of REST and facilitating the handling of calls for both client-side and server-side applications. This API is backed by the Restlet Engine and both are now shipped in a single JAR (“org.restlet.jar”).

This separation between the API and the implementation is similar to the one between the Servlet API and Web containers like Jetty or Tomcat, or between the JDBC API and concrete JDBC drivers.