...

Components

J2G consists of three executable utilities with basic Eclipse IDE UI extensions. The "Configurator" component, and the three major components, each of which have relatively specific functions, and must be run in the order as follows.

...

To run this component, navigate to bin, and run j2g-configure

...

This will automatically copy the contents of the ./plugins, ./properties, and ./compatibility directories to ECLIPSE_HOME/plugins, as well as make changes to (or create, if necessary) ECLIPSE_HOME/configuration/config.ini.

...

It is strongly advised to create a backup of the application source before running J2G

...

Below is an example of the default class_analogies.properties file

...

...

Below is an example of the default compatible_sources.properties file

...

Running the Source Identification Tool - Eclipse GUI

...

To run this component, execute the following command from the j2g bin directory, with <APPLICATION> representing the path to the application you are converting, and <GERONIMO_HOME> representing the path to Geronimo 1.1.1.

*nix

...

...

Windows

...

Note: To specify multiple sources for conversion, simply separate them with ,s (commas), as follows.

...

After the tool runs (which may take a few seconds, depending on system speed and the complexity of the application), it will display all warnings and errors to console output. These messages should be interpreted and corrected as seen fit by the user. Once changes have been made, the sources tool can be ran again to verify correctness.

...

Any references beyond the table above must be manually corrected so that they are no longer dependent on parts of JBoss.

...

...

JBoss has their own EJB annotation extensions. These must be manually corrected as needed

...

Specifying additional annotations

...

In the case of a standard EJB annotation

...

Where <annotation> is a standard EJB annotation

In the case of a standard jBoss specific to Geronimo compatible relationship

...

...

Where <j_attribute> is a JBoss supported attribute and <g_attribute> is a Geronimo supported attribute

Finally, in the case of needing multiple attribute mappings for a single annotation

...

Where <j_attribute> is a JBoss supported attribute and <g_attribute> is a Geronimo supported attribute

Below is an example of the default annotation_differences.properties file

...

...

OpenEJB

When the tool checks for usage of EJB references incompatible with Geronimo, these JBoss EJB references are automatically replaced with Geronimo compatible OpenEJB references. Here is are the differences specified to change in the persistence.xml (used in EJB 3.0) so that the configurations are consistent.

...

Below is an example of the default persistence_differences.properties file

...

In order to just suggest to the user that X may be a replacement for Y (this is conditional because this is not a direct translation) the property can be written as <Y> = suggestion:<X>.

...

To start the Descriptors Conversion Tool run the following command from the j2g bin directory, again where <APPLICATION> represents the path to the application to be converted

*nix

...

Windows

...

The warnings given in the output of this tool will report only unsupported elements that cannot be automatically converted, and must therefore be manually resolved and converted. This process is heavily dependent on the structure of the application being converted, and is therefore beyond the scope of this document.

...

To start the Resource Migration Tool run the following command from the j2g bin directory, again where <APPLICATION> represents the path to the application to be converted

*nix

...

...

Windows

...

The tool will output the name of each resource that is to be migrated, as well as informational, error, and warning messages with associated file names and line numbers. If migration of a resource is completed without errors, the tool will output a success message and generate the migrated resource in the same folder as the original one.

...