This document describes how to build/run Spring bean container support for Apache James

1. Preparations

1.1 Fetch James Server from TRUNK from svn and build

svn co http://svn.apache.org/repos/asf/james/server/trunk
cd trunk
ant dist

1.2 Build James running "ant"

2. Considering some configuration

if you are not root/Administrator on your machine or have a mail server already running on some privileged port,
it is recommended to change in file
    spring-deployment/src/main/config/james/spring-beans.xml
line
                <!--<ref bean="privilegedPortsConfigurationInterceptor" />-->
into 
                <ref bean="privilegedPortsConfigurationInterceptor" />
this will start all services at non-privileged ports. This is for testing only, as it makes your server instance
more or less incompatible with the rest of the emailing universe.

3. Building and Running

cd spring-deployment
ant run

4. JMX

Enabling: Uncomment the JMX section in spring-beans.xml
Connecting: The default connection URL defined in this file is 
  service:jmx:rmi://localhost/jndi/rmi://localhost:1099/jamesmailserver
You can use this URL on the command line under Java 1.5 (or newer) like this:
  jconsole service:jmx:rmi://localhost/jndi/rmi://localhost:1099/jamesmailserver
You will find the Processor/Mailet/Matcher tree under "Phoenix" and the other management beans under "beans". 

A. Updating configuration files

The configuration files are taken nearly unchanged from James module 'phoenix-depoyment'.
To update spring-deployment to latest from phoenix-deployment, copy files
  james-assembly.xml
  james-config.xml
  james-fetchmail.xml
  james-listmanager.xml
  james-liststores.xml
  james-xmtphandlerchain.xml
  mailboxManagerSqlResources.xml
  miResources.xml
  sqlResources.xml
from 
  trunk/phoenix-deployment/src/conf
to 
  spring-deployment/src/main/config/james