Chapter 3. Using the Jboss2jonas Migration Tool

In order to assist with conversion from JBoss to JOnAS configuration, we have provided a utility that will transform the JBoss specific configuration files into their JOnAS counterparts. The utility supports the following options:

Usage: jboss2jonas <options> > jonas-ejb-jar.xml

  This utility can be used to generate a JOnAS specific deployment
  descriptor based on an ejb-jar file and various JBoss specific
  configuration files.

Options:

    --help
        display usage information

    --ejb-jar
        the path to the ejb-jar.xml file

    --jboss
        the path to the jboss.xml file

    --jbosscmp-jdbc
        the path to the jbosscmp-jdbc.xml file

This utility will ignore JBoss configuration it doesn't (yet) understand, so it may still be necessary to migrate some of your configuration by hand, but you should still be able to use the utility to get a head start on your migration. Here is how the script is used to produce a jonas-ejb-jar.xml file from its JBoss counterparts:

prompt% cd META-INF
prompt% jboss2jonas --ejb-jar ejb-jar.xml --jbosscmp-jdbc jbosscmp-jdbc.xml --jboss jboss.xml > jonas-ejb-jar.xml

For simple applications it is not always necessary to have a jbosscmp-jdbc.xml or even a jboss.xml file. In these cases it is not necessary to specify those arguments to the jboss2jonas utility. Simply invoke it like so:

prompt% jboss2jonas --ejb-jar ejb-jar.xml --jboss jboss.xml > jonas-ejb-jar.xml

or

prompt% jboss2jonas --ejb-jar ejb-jar.xml --jbosscmp-jdbc jbosscmp-jdbc.xml > jonas-ejb-jar.xml

or even

prompt% jboss2jonas --ejb-jar ejb-jar.xml > jonas-ejb-jar.xml

This last form can be useful for creating the boilerplate jonas-ejb-jar.xml file required by jonas.