General Considerations When Upgrading to 10.x

This topic provides a list of changes you may need perform when upgrading projects to 10.x from any pervious versions of Workshop.

Errors When Upgrading/Migrating Runtimes with Custom Names

If your project contains runtimes with names different from their default names, you may see errors when you attempt to import or migrate the project into Workshop 10.x.

For example, if your Workshop 9.2 project's runtime has been defined with a name different from the default name of "WebLogic v9.2", then Workshop 10.x will not be able to recognize the runtime during the upgrade process. This will cause the following error in the Problems view.

Target runtime WebLogic v9.2 is not defined.       
The project was not built since its build path is incomplete. Cannot find the class file for java.lang.Object. Fix the build path then try building this project       
The type java.lang.Object cannot be resolved. It is indirectly referenced from required .class files

To repair your project's runtime reference, right-click the project and select Properties. In the Properties dialog, click Targeted Runtimes. Select the desired runtime and click OK.

Problems with Library Module References in Classpaths and Deployment Descriptors

After upgrade, your project's library module references on the classpath and in the deployment descriptors may be out of sync. (This can happen if the project's library module references were manually edited before upgrade.) If the references are out of sync, you will see one of these errors:

• Unable to resolve the reference to "<library-name>" library on project classpath.
• Unable to resolve the reference to "<library-name>" library in the deployment descriptor.
• "<library-name>" library is on the classpath of this project, but is not in the weblogic-application.xml file of the EAR project "<EAR-project-name>".
• "<library-name>" library is on the classpath of this project, but is not in the weblogic.xml file.
• "<library-name>” library is a web library and can only be referenced on the classpath of a web project.
• "<library-name>" library reference is not allowed in the weblogic.xml file. Only WAR libraries are allowed.
• This project must be part of an ear in order to use library "<library-name>".
• The reference to the "<library-name>" library on this project's classpath differs from the reference to this library in the weblogic-application.xml file of the EAR project "<EAR-project-name>".
• The reference to the "<library-name>" library on this project's classpath differs from the reference to this library in the weblogic.xml file.

For detailed information on correcting the library module references, see WebLogic J2EE Libraries - Problems.

Upgrade Requires Installation of Weblogic Server and Workshop to Their Default Locations

For Workshop versions 9.2 and after, project upgrade is not supported when either WebLogic Server or Workshop are not installed to their default locations.

For version 10.3, the default locations are:

• WebLogic Home: <BEA_HOME>/wlserver_10.3
• Workshop Home: <BEA_HOME>/workshop_10.3

What To Do When Upgrade Fails

If upgrade fails for some reason, use source control system to revert the application files to their pre-upgrade state and delete any files created by the unsuccessful upgrade attempt. If you attempt upgrade again, make sure that all application files are checked out.

On upgrade failure, files are not reverted to their original state

When an upgrade fails the new files are not reverted to their original state but may not be fully upgraded. For example, the file extension may have been changed to .java, but annotations may not have been translated to the current version. Note that the original source files are not altered. In this case, either drag and drop the file into the workspace and perform upgrade on that file again or re-import the entire project.