® Expeditor 6.1.2 and Lotus
Expeditor 6.2.0, a significant repackaging resulted in the consolidation of language fragments from .nl1, .nl2, .nl2a, .nlBidi, and .nl3 into a single fragment identified as .nl. These changes will not affect public APIs or Extension Points.
The plug-in com.ibm.rcp.platform
has been moved from the com.ibm.rcp.personality.framework.feature
to the com.ibm.rcp.wed60.compatibility.feature
. If you have dependencies on this plug-in, either remove the dependencies, or install the compatibility feature.
The following plug-in references may exist in the additional.bundles
property in the build.properties
file of Client Services projects. These plug-ins have been removed. To correct issues with projects, select the project, then right click and select Properties > Client Services
. If you need no other changes to the target platform, then just click OK
. Otherwise, make any other need changes to the target for this plug-in, then click OK
. The additional.bundles
property will be updated upon save.
The following plug-in re-exported packages from the com.ibm.pvc.servlet
plug-in and has been removed. Following the steps in Taking corrective action
below to resolve any issues.
The following plug-in provided classes were deprecated in previous releases and have now been removed. If plug-ins are still referencing these classes, then you will need to update the project to use the declarative web application definitions, or to use the appropriate classes for web application activators. Refer to the Web Container / Web Application Javadoc for information on the class definitions.
The following plug-ins provided support for the Embedded Transaction Container which has been removed in Lotus
The following plug-in was removed from the platform. While it is unlikely it was referenced by other plug-ins, it did previously contribute actions to the menus. Those actions have been moved to the com.ibm.rcp.provisioning.ui
plug-in. If Eclipse activities were defined that referenced this plug-in, the activity definitions must be updated.
The following plug-ins have been removed. It is unlikely that these will cause runtime or development issues. If problems are encountered, then refer to the Taking corrective action
- com.ibm.rcp.jcl.desktop.linux.x86 (replaced with com.ibm.rcp.dee.linux.x86)
- com.ibm.rcp.jcl.desktop.win32.x86 (replaced with com.ibm.rcp.dee.win32.x86)
- org.apache.portals.bridges.jsf (replaced with org.apache.portals.bridges)
Taking corrective action
There are two methods for taking corrective action:
- Removing the dependency
- Adding your own compatibility plug-ins
To remove the dependency, you will need to edit the MANIFEST.MF
) to remove from the plug-in dependencies attribute any plug-ins shown above. You will then need to re-deploy the application with the changes.
To add your own compatibility plug-in to fulfill any plug-in dependencies, you will need to create a new plug-in in your workspace.
- Select File > New > Project > Client Services > Client Services Project.
- Use the plug-in name as the project name, and deselect Create a Java™ project, then select Next.
- Fill in any ID, Name, Version or Provider information that you wish to change, then select Finish.
You will then need to deploy the compatibility plug-in with your application plug-ins. You may also use a standard Eclipse Plug-in Project to create a new compatibility plug-in.
After you have either removed the dependency, or have created a new compatibility plug-in, you may see compilation errors as a result of missing packages or classes. You will need to use only public APIs.
Refer to the Javadoc describing publicly available APIs.
Parent topic: Migrating component logic