Declares a binding to the CONNECT http method

Declares a binding to the DELETE http method

Declares a binding to the GET http method

Declares a binding to the HEAD http method

Declares a binding to the OPTIONS http method

Declares a binding to the POST http method

Declares a binding to the PUT http method

Annotate a controller to define its route

Declares a binding to the TRACE http method

Http CONNECT

Http DELETE

Http GET

Http HEAD

Http OPTIONS

Http POST

Http PUT

A route configuration

Http TRACE

Create an 500 status response

Create an 404 status response

Create an 200 status response

Run a basic application example.

A Cayla application.

Creating a Cayla application

An application is created by provided a container in which controllers are discoved.

Object container

Creates an application with a top level container object, the object is scanned for the nested controllers.

object controllers {
  route("/")
  shared class Index() {
    shared actual default Response handle() => Response.ok().body("Hello World");
  }
}
void run() {
  value application = Application(controllers);
  application.start();
  process.readLine();
}

Package container

Creates an application with a package container object, the package is scanned for the nested controllers.

void run() {
  value application = Application(`package my.application`);
  application.start();
  process.readLine();
}

Application life cycle

The start method starts the application and returns a Runtime Promise which:

• is resolved with the Runtime object when the application is fully started
• is failed with the reason of the failure when the application cannot be started

This Promise can be used to be aware of the application life cycle:

Promise<Runtime> runtime = application.start(); 
runtime.always((Runtime|Exception arg) => print(arg is Runtime then "started" else "failed: ``arg.string``"));

The body response extends the Status with a body

The base class for web controllers. A controller must extend this class, its attributes are mapped to the request parameters.

Attributes of this class should:

• declares the String type (later Boolean, Integer, etc…)
• be shared
• be immutable

A controller serves two purposes: . to serve a request . to produce an URL that will provide an address for this controller

route("/")
shared class Index() extends Controller() {
  shared actual default Response handle() => Response.ok().body("Hello World");
}

Our Index controller:

• extends the Controller interface
• is mapped to the server root via the [route] annotation
• overrides the handle method for serving the default page

Mapping a request parameter to the controller can be achieved by declaring a corresponding attribute:

route("/greeter")
shared class Greeter(String name) extends Controller() {
  shared actual default Response handle() => Response.ok().body("Hello ``name``");
}

The Greeter controller is mapped to the /greeter path and can be invoked with an URL like /greeter?name=Cayla.

The parameter can also be mapped to a path parameter by specifying it in the path:

route("/greeter/:name")
shared class Greeter(String name) extends Controller() {
  shared actual default Response handle() => Response.ok().body("Hello ``name``");
}

The controller string produces an URL for invoking this controller, the URL is generated using:

• the path declared by the route annotation
• the controller attributes

Let's redefine our Index controller:

route("/")
shared class Index() extends Controller() {
  shared actual default Response handle() => Response.ok().body("Say hello to <a href="``Greeter("Cayla")``">Cayla</a>");
}

The response body will contain an URL that will look like http://localhost:8080/greeter?name=Cayla. The URL would be http://localhost:8080/greeter/Cayla when using path parameter mapping.

The string method redefined by the base Controller class:

• takes care of generating the correct URL, including the parameter encoding
• provides a safe way for generating URL that is enforced by the Ceylon compiler and is refactorable in the Ceylon IDE

When more context is required during the request, the invoke method can be overriden instead of the handle method. The RequestContext class provides access to the full content of the request.

The request context provides the information available during a request such as:

• the Vert.x request
• generating an URL for a controller

The response to a request.

The application runtime.

The runtime is obtained from the Application.start method.

A status response provides a simple http response with a status code and headers.