Compatibility plug-ins providedAdded by IBM on October 4, 2010 | Version 1 (Original)
Many capabilities provided by WebSphere® Everyplace® Deployment 6.0 have been updated in this version of the client platform. The following compatibility plug-ins have been provided to ease migration to the current client platform. If you had plug-in requirements on com.ibm.eswe.workbench
, you should make the following changes in order to improve future compatibility and migration.
This plug-in provided the user interface for the WebSphere Everyplace Deployment 6.0 platform. Two extension points, com.ibm.eswe.workbench.WctApplication and com.ibm.eswe.workbench.WctWebApplication, were provided to enable contributions to the application launcher. These extension points are still provided, but the plug-in identifier has changed.
If you used these extension points, the Eclipse Plug-in Project or the Client Services projects created using previous editions of the tools may have added a statement to the plug-in manifest to create a dependency on this plug-in. Specifically, the com.ibm.eswe.workbench may have been added as a plug-in dependency.
Corrective action: Remove com.ibm.eswe.workbench from the plug-in dependency list. You may continue to use the extension points
This plug-in provided additional Unicode capability beyond the capability provided by the Java standard class libraries. In WebSphere Everyplace Deployment 6.0, this plug-in provided ICU4J v3.2.0 packages. In this release, Eclipse has provided v3.4.5, but in a plug-in named com.ibm.icu.
Plug-ins written to use the ICU4J packages provided by the com.ibm.icu.icu4j plug-in provided by WED 6.0 may have the plug-in com.ibm.icu.icu4j listed as a plug-in dependency. An implementation of the com.ibm.icu.icu4j has been provided in this release that re-exports the packages from com.ibm.icu.
Corrective Action: The preferred method is to switch from a plug-in dependency on com.ibm.icu.icu4j to do an Import-Package on the packages from com.ibm.icu that you need to use. Alternatively, you can change the dependency from com.ibm.icu.icu4j to com.ibm.icu.
This plug-in previously provided extension points that were deprecated. It also re-exported packages from the com.ibm.rcp.personality.framework
As this plug-in has been deprecated, you should update any dependencies on it.
Refer to the following table to determine which extension point references should be updated
|Extension point provided by com.ibm.rcp.platform||Extension point you should used instead|
|com.ibm.rcp.platform.PlatformInitialization||This extension point was removed completely. As a result, use Platform Lifecycle to contribute plug-ins to platform startup. For more information on plug-ins removed from this release, refer to Plug-ins removed in this release.|
|com.ibm.rcp.platform.personalities ||com.ibm.rcp.personality.framework.personalities |
|com.ibm.rcp.platform.personalityStartup ||com.ibm.rcp.personality.framework.personalityStartup |
|com.ibm.rcp.platform.personalityExtensions ||com.ibm.rcp.personality.framework. personalityExtensions |
Plug-ins that have a Require-Bundle
should change the dependency to com.ibm.rcp.personality.framework
Parent topic: Migrating component logic: XPD621