import xitrum.Action
import xitrum.annotation.GET

@GET("url/to/HelloAction")
class HelloAction extends Action {
  def execute() {
    val urlToHelloActor = url[HelloActor]
    respondHtml(
      <xml:group>
        <p>Hello {remoteIp}!</p>
        <a href={urlToHelloActor}>Actor sample</a>
      </xml:group>
    )
  }
}
            

import scala.concurrent.duration._
import akka.actor.ReceiveTimeout
import xitrum.{ActionActor, Config}
import xitrum.annotation.GET

@GET("url/to/HelloActor")
class HelloActor extends ActionActor {
  def execute() {
    logger.info("Actor started, remoteIp: " + remoteIp)

    val anotherActorRef = actorFor("someService")
    anotherActorRef ! "someRequest"

    context.setReceiveTimeout(5.seconds)
    context.become {
      case someResponse =>
        respondText("Response: " + someResponse)

      case ReceiveTimeout =>
        respondText("Timeout")
    }
  }

  override def postStop() {
    logger.info("Actor stopped")
  }
}
            

import xitrum.{
  Action, WebSocketActor,
  WebSocketText, WebSocketBinary,
  WebSocketPing, WebSocketPong
}
import xitrum.annotation.WEBSOCKET

@WEBSOCKET("url/to/EchoWebSocketActor")
class EchoWebSocketActor extends WebSocketActor {
  def execute() {
    logger.info("onOpen, remoteIp: " + remoteIp)

    context.become {
      case WebSocketText(text) =>
        respondWebSocketText(text)

      case WebSocketBinary(bytes) =>
        respondWebSocketBinary(bytes)

      case WebSocketPing =>
        // Xitrum automatically sends pong for you,
        // you don't have to send pong yourself

      case WebSocketPong =>
        // Client has received your ping
    }
  }

  override def postStop() {
    logger.info("onStop")
  }
}
            

import xitrum.{Action, SockJsActor, SockJsText}
import xitrum.annotation.SOCKJS

@SOCKJS("url/to/EchoSockJsActor")
class EchoSockJsActor extends SockJsActor {
  def execute() {
    logger.info("onOpen, remoteIp: " + remoteIp)

    context.become {
      case SockJsText(text) =>
        respondSockJsText(text)
    }
  }

  override def postStop() {
    logger.info("onStop")
  }
}
            

Features

• Typesafe, in the spirit of Scala. All the APIs try to be as typesafe as possible.
• Async, in the spirit of Netty. Your request proccessing action does not have to respond immediately. Long polling, chunked response (streaming), WebSocket, and SockJS are supported.
• Fast built-in HTTP and HTTPS web server based on Netty. Xitrum’s static file serving speed is similar to that of Nginx.
• Extensive client-side and server-side caching for faster responding. At the web server layer, small files are cached in memory, big files are sent using NIO’s zero copy. At the web framework layer you have can declare page, action, and object cache in the Rails style. All Google’s best practices like conditional GET are applied for client-side caching. You can also force browsers to always send request to server to revalidate cache before using.
• Routes are automatically collected in the spirit of JAX-RS and Rails Engines. You don’t have to declare all routes in a single place. Think of this feature as distributed routes. You can plug an app into another app. If you have a blog engine, you can package it as a JAR file, then you can put that JAR file into another app and that app automatically has blog feature! Routing is also two-way: you can recreate URLs (reverse routing) in a typesafe way.
• Views can be written in a separate Scalate template file or Scala inline XML. Both are typesafe.
• Sessions can be stored in cookies (more scalable) or clustered Hazelcast (more secure). Hazelcast is recommended when using continuations-based Actions, since serialized continuations are usually too big to store in cookies. Hazelcast also gives in-process (thus faster and simpler to use) distribued cache and pubsub, you don’t need separate cache and pubsub servers.
• jQuery Validation is integrated for browser side and server side validation.
• i18n using GNU gettext. Translation text extraction is done automatically. You don’t have to manually mess with properties files. You can use powerful tools like Poedit for translating and merging translations. gettext is unlike most other solutions, both singular and plural forms are supported.
• Xitrum tries to fill the spectrum between Scalatra and Lift: more powerful than Scalatra and easier to use than Lift. You can easily create both RESTful APIs and postbacks. Xitrum is controller-first like Scalatra, not view-first like Lift. Most people are familliar with controller-first style.

Scalibility is easy, just throw more nodes to the pool.

sbt/sbt run