Most of the work is done and checked in. However, detecting the right JMS properties file is only implemented for GlassFish at the moment. I still have to do this for our other support J2EE application servers.

Detecting the right JMS properties file is now implemented for JBoss and clustered JBoss as well.

To explain the detecting part of the right JMS properties a bit more in detail, the framework does the following at the moment:

• If the com.icesoft.net.messaging.properties is not defined in the web.xml the framework examines the Server Info string to see which application server is used
• If GlassFish is detected the default glassfish.properties is used; if this fails the framework cannot use the JMS functionalities automatically.
• If JBoss is detected the default jboss_ha.properties is used first; if this fails because a clustered environment is not used the default jboss.properties is used instead; if this fails as well the framework cannot use the JMS functionalities automatically.

I still have to add support for our other supported application servers, but this will be targeted for 1.7.2

Marking this one as FIXED.

JBoss auto-detection for the JMS properties fails on JBoss 4.0.x. Reopening this one.

The Server Info string on JBoss 4.0.x starts with "Apache Tomcat". Auto-detection for JBoss 4.0.x is now updated. Marking this one as FIXED again.