JBoss Inc.

JBoss 4.0.5.CR1 Release Notes

This is the jboss-4.0.5.CR1 release for the Java EE™ 1.4 codebase. For information on the APIs that make up Java EE 1.4, see Java EE v1.4 Documentation. For a comprehensive tutorial on Java EE 1.4, see The Java EE™ 1.4 Tutorial. A jboss-4.0.x getting started guide that is based on contents from the tutorial can be found in JBoss Application Server Documentation Library

JBoss releases follow our new product versioning rules.

Note: The JBossAS installer allows for arbitrary profiles of the underlying microkernel, including previews of future technologies such as EJB3 which by definition are not Java EE certified. Only the default and all installer profiles with isolation/call by value enabled correspond to Java EE certified profiles.

Overview

Highlights

Plus more than 60 bug fixes, see the Detailed Release Notes section for the full details.

Compatibility Issues

This lists the changes that could affect compatibility.

Configuration Issues

This lists the changes that could affect configuration.

Note that as of the 4.0.1 release, the distributed configurations have switched back to the 3.2.x types of distribution configurations:

The standard configuration from the 4.0.0-4.0.1RC1 releases has been dropped and the default flat class loading model from 3.0.x-3.2.x has been restored for the default configuration. This change in behavior was done to restore consistency with the 3.2.x class loading model. The 4.0.0 scoped class loading behavior and call by value JNDI lookup behavior can be restored by:

  1. Editing conf/jboss-service.xml and setting the NamingService CallByValue to true: 
             <mbean code="org.jboss.naming.NamingService"
         name="jboss:service=Naming">
         <!-- The call by value mode. true if all lookups are unmarshalled
         using
         the caller's TCL, false if in VM lookups return the value by reference.
         -->
         <attribute name="CallByValue">true</attribute>
         <!-- The listening port for the bootstrap JNP service. Set this to
         -1
         to run the NamingService without the JNP invoker listening port.
         -->
         ...
         </mbean>
  2. Editing the deploy/ear-deployer.xml and setting the Isolated and CallByValue attribute to true: 
          <server>
      <!-- EAR deployer, remove if you are not using ear deployments -->
      <mbean code="org.jboss.deployment.EARDeployer"
      name="jboss.j2ee:service=EARDeployer">
      <!-- A flag indicating if ear deployments should have their own scoped
      class loader to isolate their classes from other deployments.
      -->
      <attribute name="Isolated">true</attribute>
      <!-- A flag indicating if the ear components should have in VM call
      optimization disabled.
      -->
      <attribute name="CallByValue">true</attribute>
      </mbean>
      </server>

Library Updates

JBoss Library Updates

Thirdparty Library Updates

Detailed Release Notes

Includes versions: JBossAS-4.0.5.CR1

Feature Request

Bug

Task

Sub-task

Documentation and Help

Documentation and help may be obtained from the JBoss site.

Licenses

JBoss is licensed under the LGPL. The licence texts for JBoss and the thirdparty components it uses may be found in the docs/licenses directory of the distribution. Browse Licences

About JBoss, a division of RedHat

JBoss, a division of RedHat, is in the business of providing superior technical support to our customers. Our goal is to make Professional Open Source™ the SAFE CHOICE for you. We accomplish this by backing up our open source Java products with technical support services that are delivered by the core developers themselves. We can help you to train your staff and provide you with support at every stage of the application lifecycle - from development and integration through deployment and maintenance. Visit the JBoss Services page for more information.