Resin organizes resources and classloaders into nested environments. Each environment context merges its own configuration with configuration inherited from the parent environment. Each environment context: server, host, web-app, etc. may be configured with any of the environment configuration tags.

A web application is a self-contained subtree of the web site. It has a distinct Application object (ServletContext), sessions, and servlet mappings.

Description of the resin.conf configuration.

Resin can perform access logging, specify where JDK 1.4 logging interface messages go, and redirect the stderr and stdout for your applications.

Resin's configuration files support JSP EL expressions in several contexts.

With Resin, the init tag configures Java Bean-style objects. A "Java Bean" is just a Java class that follows a simple set of rules. Because Resin can find the bean-style setters from looking at the class, it can configure those setters in a configuration file like the web.xml.

Alphabetical index of all configuration tags.

Virtual Hosting

Each Resin instance can serve many virtual hosts.

Reliability and Load Balancing

As traffic increases, web sites need to add additional web servers and servlet engines.

Persistent and Distributed Sessions

Sessions can be persistent across server restarts, including application restarts when classes change.

TCP-Ring Distributed Sessions

Performance Tuning

ISP with Apache

Resin Environment Relax-NG Schema

The formal definition for the Resin environment configuration.

Resin J2EE common Relax-NG Schema

The formal definition for the Resin common J2EE definitions.

Resin web.xml Relax-NG Schema

The formal definition for the Resin web.xml configuration.

resin.conf Relax-NG Schema

The formal definition for the resin.conf configuration.

Resin J2EE common Relax-NG Schema

The formal definition for the strict J2EE definitions.

Resin J2EE web.xml Relax-NG Schema

The formal definition for the strict J2EE web.xml.

Where can I find the .rnc files that Resin uses for validating configuration files?

A repository of notes and comments that will eventually make their way into the documentation. Please treat the information here with caution, it has often not been verified.

alternative to making resin executable for binding to port 80 on Linux?