The Java™ EE upgrade
wizard supports the migration from J2EE 1.2, 1.3 and 1.4 specifications
to the Java EE 5.0 specification
level for all Java EE module
types. The wizard also supports migration from Java EE 5.0 to Java
EE 6.0 specification level for all Java EE module types.
About this task
Refer to
J2EE 1.3 to 1.4 specification level upgrade and
J2EE 1.2 to 1.4 specification level migration for details on the migration of
J2EE 1.3 and 1.2 specification level artifacts to J2EE 1.4 specification
level. Using the Java EE specifications upgrade wizard, you can upgrade
any Java EE 5 and pre-Java EE 5 module to Java EE 6. See the following
table for more module version details:
Table 1. Java EE version
numbers| Module type |
J2EE |
Java EE 5 |
Java EE 6 |
| Web |
2.2 |
2.5 |
3.0 |
| EJB |
1.1 You can migrate EJB 1.1 to EJB 3 or EJB
3.1, providing that there are no CMP or BMP beans (EJB 1. x and 2.
x projects with CMP or BMP beans can be left as is in a Java EE EAR).
|
3.0 |
3.1 |
| JCA |
1.0 |
1.5 |
1.6 |
| EAR |
1.2 |
5.0 |
6.0 |
| Application Client |
1.2 |
5.0 |
6.0 |
For more information, see EJB 3.0 module considerations
Note: Before
using the Java EE upgrade wizard, it is recommended that you take
the following steps:
- Back up your entire workspace.
- If you are working with a shared repository, check out or lock
all corresponding projects.
Procedure
- In the Enterprise Explorer view of the Java EE perspective, right-click the enterprise
application project that you want to upgrade.
- Right-click the project that you want to upgrade, and select .
- Follow the instructions on the Java EE Specifications Upgrade wizard Welcome
Page before proceeding with the migration process, and click Next.
- In the J2EE version field, select
the Java EE version level you
want to upgrade to, and click Next.
- Select the modules you want to upgrade, and click Finish. Modifications made by the migration
process:
- Increases the version level of the project facet:
- Before migration:
- After migration:
- Converts .xmi files from older Java specification levels into .xml files:
- Before migration:
- After migration:
Modifications not made by the migration process:- Migration does not create new EJB 3.0 or EJB 3.1 business interfaces.
- Migration does not convert deployment descriptor values into Java EE annotations within your Java code.