A new cookbook showing the new parameterized configuration for resin.xml. The resin.xml can now import a properties file and use the properties as EL expressions like ${http} to create clean configurations. The example shows a simple, but complete cluster of three Resin servers acting as http servers, including the health system.

wiki4: Resin Application Server: Parameterized Web Server Cluster

Another cookbook at wiki4: Resin Messaging: JMS Topic Configuration with CDI and JNDI as requested by a customer.

The cookbook will be interesting if you want to see a relatively-complicated Resin CDI configuration which includes JNDI for the purpose of Spring integration, and also showing how custom facades can be combined with a standard JMS Topic configuration.

I’ve added a wiki cookbook on Resin WebSockets and Hessian.

wiki4: Resin Messaging: WebSockets with Hessian

Note, that this is a binary websocket protocol, so it would be used with a custom websocket client, not a browser. Since the browsers currently prefer speaking text websockets, the equivalent would be a JSON server.

As a request from a user, I’ve written up a short wiki cookbook for Resin 4.0’s URL rewrite for a security rule to require SSL for a section of a website.

Wiki: Resin Web Server: URL Rewrite Forbidding non-SSL Requests

The example is pretty simple, since it just needs the as the action rule, and a single predicate, to test the request. Because it’s simple, it’s a good introductory example of Resin’s URL rewriting for people who haven’t looked into it yet.

I’ve written up a quick how-to for configuring a Resin jCache ClusterCache and injecting it with CDI. The application code uses standard classes and CDI annotations and uses the Resin jCache implementation.

http://wiki4.caucho.com/Resin_Java_Cache_using_CDI_Inject

When you’re using Hessian in a streaming environment like WebSockets, you can improve performance by saving the serialization reflection and reusing the input and output streams.

See http://wiki4.caucho.com/Hessian_Performance_OutputStream for a short cookbook example.

Since I published Part 1 of the Resin Command Line Overview we’ve added a few more commands. The added commands allows to enable or disable a server, add a license, deploy new configuration files and generate admin password. Today I hope to cover commands I did not cover in part on and the new commands. (more…)

Conditional Configuration Using Functions and Expressions

This second part of a multi-part article on Resin configuration examines how to employ conditional XML statements and EL functions to simplify Resin configuration. When we’re done, you’ll understand how the same configuration could be shared between deployment environments with entirely different Resin operation by using some following concepts:

• Conditional XML with <resin:if>, <resin:when>, <resin:choose>, <resin:otherwise>
• Null checking with “the Elvis Operator” ?:
• Regular expression matching with =~
• Resource access with mbean() and jndi()

(more…)

Charles Humble talks to Paul Cowan about the Resin Application Server architecture, capabilities, and where it fits in the Cloud market. You can see the video interview on InfoQ.