J2EE tools Release Notes

© Copyright International Business Machines Corporation 2006. All rights reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM® Corp.

Release notes

1.0 Known problems and workarounds
   1.1 Importing J2EE Projects using SCM Clearcase adapter
   1.2 Browse button in the servlet detail section of Web deployment descriptor editor does not work
   1.3 Reflection errors from EJB validator with XDoclet annotated EJB Project Interchange file
   1.4 All J2EE Projects have project specific compiler settings
   1.5 Missing Java source during WAR import on Linux® with auto build
   1.6 New J2EE Module wizards incorrectly specify EAR server runtime version
   1.7 Migrating J2EE Projects - need to wait for build to complete
   1.8 Migrating J2EE Projects - Error message "need to migrate WTP metadata"
   1.9 Open EJB Visualizer and EJB Deployment descriptor editors can cause exception

1.0 Known problems and workarounds

1.1 Importing J2EE Projects using SCM Clearcase® adapter

If you are importing projects from ClearCase using the "Import from existing Project" dialog, the imported project may be missing the "Deployment Descriptor" node in the Project Explorer view.

Workaround: Close and reopen your workspace. 

1.2 Browse button in the servlet detail section of Web deployment descriptor editor does not work

The Browse button for the servlet class in the Servlet detail section of the Web deployment descriptor editor does not work.

Workaround: Use the Source page to edit the servlet class attribute.

1.3 Reflection errors from EJB validator with XDoclet annotated EJB Project Interchange file

If you have auto build turned on and import using project interchange, you may see reflection errors.  You may also see errors if you manually build projects with auto build turned off.

Workaround: Close and reopen the project.

1.4 All J2EE Projects have project specific compiler settings

J2EE Projects  (Web, EJB, EAR, Connector, Java Utility, App Client) will add project level compiler settings using defaults from jre level used. If non-default workspace compiler preferences were set, the project level settings may need to be removed by either deselecting "Enable project level settings", or deleting the /.settings/org.eclipse.jdt.core.prefs.

1.5 Missing Java source during WAR import on Linux with auto build

In some instances on Linux, EAR import fails to properly import nest WAR archives Java source files if auto build is on.

Workaround: Disable auto build prior to import. The same workaround may be helpful if this happens with WAR import.

1.6 New J2EE Module wizards incorrectly specify EAR server runtime version

Situations can arise when creating multiple J2EE module projects under multiple ears targeted to different runtime versions.

The target runtime field is disabled when adding to an existing EAR (should inherit the EAR version), but sometimes this version is incorrect, and to refresh, the "Add to EAR" check box should be toggled (selected and cleared) twice.

1.7 Migrating J2EE Projects - need to wait for build to complete

After V5.1.2/V.6 projects are imported into a V7.0 workspace, and builder is activated to migrate the existing metadata into a V7.0 style.

On large workspaces, this build can take several minutes, and these projects should remain untouched until the process is complete. If you did not wait for the build to complete after importing projects and encountered any problems such as a WebSphere® Server Warning prompt when trying to open the Deployment page of an imported EAR, then close your workbench and reopen it.

1.8 Migrating J2EE Projects - Error message "need to migrate WTP metadata"

During project migration, the operation may fail leaving the project in a semi-migrated state. 

Workaround: In the Resource perspective, open the ".project" file in the project root, and delete the following entry:

<nature>org.eclipse.wst.common.modulecore.ModuleCoreNature</nature>

Then restart the workbench and run a clean build. This will reactivate migration on this project.

1.9 Open EJB Visualizer and EJB Deployment descriptor editors can cause exception

When you are creating new elements in the EJB Visualizer editor and the EJB Deployment Descriptor editor is open to the "References" page, exceptions can occur, causing errors in the generated EJB elements.

 Workaround: Close the EJB Deployment Descriptor editor before working with the EJB Visualizer editor.