Xitrum 3.14: Autoreload classes and support both Scala 2.11.x and 2.10.x

44 views
Skip to first unread message

Ngoc Dao

unread,
Jun 14, 2014, 11:17:01 PM6/14/14
to xitrum-f...@googlegroups.com
Happy World Cup!

The Xitrum team would like to announce Xitrum 3.14 (Xitrum π):

This version adds some big features:

1. Autoreload classes and recollect routes in development mode

See screencast:

Under the hood, in development mode Xitrum uses its file monitoring feature (http://xitrum-framework.github.io/guide/howto.html#monitor-file-change) to monitor the directory target/scala-<version>/classes. When there's a change, at the next request Xitrum will create a new class loader to load the new/modified classes.

2. xitrum.Component

You can create reusable view components that can be embedded to multiple views. See the Xitrum Guide Book:

3. Allow the use of OpenSSL engine for faster HTTPS

This is a feature of the network library Netty that Xitrum uses:

To enable the OpenSSL engine, Apache Portable Runtime (APR) and OpenSSL must be in the library load path such as system library directories, $LD_LIBRARY_PATH (Linux, Mac), and %PATH% (Windows).

In old xitrum.conf:

```
keystore {
  path                = config/keystore.jks
  password            = xitrum
  certificatePassword = xitrum
}
```


```
https {
  useOpenSSL    = false
  certChainFile = config/ssl_example.crt
  keyFile       = config/ssl_example.key
}
```

Xitrum 3.14 has updated Netty to its latest version 4.0.20:

4. Support both Scala 2.10.x and 2.11.x

You should use Scala 2.11.x whenever possible, but because your project may use a library that has not been updated to support Scala 2.11.x, you are forced to use Scala 2.10.x.

Xitrum 3.11 to 3.13 only support Scala 2.11.x. From Xitrum 3.14 you can again also use Scala 2.10.x.

--------

To update Xitrum in your project from 3.13 to 3.14, you have to update xitrum.conf (as above) and build.sbt in your project.

Example:

Gert Thiel

unread,
Jun 15, 2014, 3:50:55 PM6/15/14
to xitrum-f...@googlegroups.com
Great news. No costly JRebel needed.
Reply all
Reply to author
Forward
0 new messages