- download a copy of JBoss4.0+ - unpack it somewhere
- set JBOSS4_HOME to this directory and export it
- Copy $WADI_HOME/lib/wadi-jboss4-*.jar to e.g. $JBOSS4_HOME/server/default/lib (contains logging integration - see below)
- Create a wadi.sar containing all the jars from $WADI_HOME/lib (except wadi-jboss4-*.sar) and a META-INF/jboss-service.xml (use e.g. $WADI_HOME/conf/jboss-service.xml)
- copy the sar into e.g. $JBOSS4_HOME/server/default/deploy
- copy $WADI_HOME/webapps/wadi-webapp-*.war into the same dir
- In $JBOSS4_HOME/bin, start your JBoss like this 'JAVA_OPTS="-Dx=... -Dy=..." ./run.sh', where x,y..z are properties from your chosen conf/node.*.properties file.
- If you are using the DiscStore, you may have to create a 'sessions' dir underneath java.io.tmpdir for WADI to page sessions in and out of.
Logging Integration :
JBoss4 uses a customised log4j (adds 'trace' level) for logging.
WADI uses the commons-logging API.
By default, WADI will log out to JBosses loggers, but WADI trace-level will be collapsed into JBoss debug-level. This can be annoying. wadi-jboss4-*.jar contains a Log class that bridges the gap between the two logging systems and channels WADI-trace to JBoss-trace. It cannot be installed via the wadi.sar, since it must be available to log4j at startup time, hence the alternate deployment location.
Actually getting trace output from JBoss can be quite problematic in itself. Here is how I achieve it.
1) Remove the 'Threshold' attribute from your <appender/> clause - Setting it to 'TRACE' does not seem to work (probably because this is a custom log level).
2) To enable WADI trace level logging, include a category clause e.g. : <category name="org.codehaus.wadi"><priority value="TRACE" class="org.jboss.logging.XLevel"/></category>.
3) In order to get the logging bridge installed add a '-Dorg.apache.commons.logging.Log=org.codehaus.wadi.jboss4.JBossLog' to your JAVA_OPTS when starting JBoss.
An example log4j.xml is included in $WADI_HOME/conf/jboss-log4j.xml. This may be copied to or merged with e.g. $JBOSS_HOME/server/default/conf/log4j.xml