Upgrade to JBoss 4.2.3

[jmoore]

Possibly even for 3.0, it may be benefitial to update to JBoss 4.2. Simply the fact of having EJB3 installed by default will make things simpler. (I'll need to check on whether or not the issue with Serializable types has been fixed, which caused us to require exact point versions. If it has, the 4.2 line could make working with JBoss a lot simpler.)

A couple of interesting changes from http://sourceforge.net/project/shownotes.php?release_id=491475&group_id=22866:

• conf/log4j.xml has been renamed to conf/jboss-log4j.xml, to allow log4j.properties override from scoped deployments, JBAS-1853.
• JDK5 is *required* to run JBossAS 4.2.x. The decision was based on the fact that JDK1.4 is phased out and the reality that a lot of people like Java Annotations support and want to combine EJB3 and JBoss Seam components with JBossAS. JDK6 is not formally supported yet, although you may be able to start the server with it. JDK6 support will come with JBossAS 5.x.
• JBoss EJB3 is now deployed *by default* in JBossAS 4.2.x The fact that we base on JDK5 makes our life easier in this regard, meaning we don't have to maintain jdk5 code retro-weaved for jdk1.4 runtimes, and we can include by default components that require jdk5 to run.
• The higly available (HA) version of the local and xa resource adapters (jboss-ha-local-jdbc.rar, jboss-ha-xa-jdbc.rar), are now consider production quality.
• .EAR files support ./lib directory, JBAS-4037.
• The default invoker for EJBs has been changed from the rmi-invoker to the unified-invoker, provided by JBoss Remoting, JBAS-3950.

[jmoore]

r2728 closes.