Applications developed for JOnAS 4.1 do not require changes; however, they should be redeployed (GenIC). The main changes occur within the JOnAS configuration files, and it is recommended that you document your customizations in the new JOnAS 4.3.2 configuration files, especially for the files mentioned below.
The most visible configuration changes are the following:
By default, JORAM uses RAR instead of the JMS service
JOnAS no longer uses the JRE ORB implementation; it uses the JacORB implementation. The default iiop model now used is the POA model (http://java.sun.com/j2se/1.4.2/docs/guide/rmi-iiop/rmiiiopexample.html). Thus, GenIC should be relaunched on all previously generated beans.
Configuration files with significant changes:
The jms service is removed from the jonas.services property.
This file is used for specifying the creation of JMS-administered objects when using the JORAM connector. The JMS destinations previously defined in the jonas.properties file (jonas.service.jms.queues and jonas.service.jms.topics) must be moved into this file.
This is the configuration file for JacORB.
If starting from an existing JONAS_BASE, it must be updated in order to upgrade to the last built-in provided EAR/WAR/JAR/RAR files (for example, new versions of the JORAM or JDBC RARs).
cd $JONAS_ROOT ant update_jonasbase |
If you want to keep the jms service and not use the JORAM's RAR, you have to remove the $JONAS_BASE/rars/autoload/joram_for_jonas_ra.rar.