You have an existing AEM application which is based on wcm.io Configuration 0.x, and you want to migration to Apache Sling Context-Aware Configuration. Maybe you are also using wcm.io Handler 0.x which is also based on wcm.io Configuration 0.x.
Supported AEM Versions
Apache Sling Context-Aware Configuration is a built-in feature of AEM 6.3, and can be deployed manually in AEM 6.1 and AEM 6.2. AEM 6.0 or older is not supported.
If you are using AEM 6.1 or 6.2 you have to deploy the following bundles additionally (latest Version):
You have different migration scenarios:
- Scenario A: Drop-in replacement via Compatibility Layer
- Scenario B: Drop-in replacement via Compatibility Layer and update to new APIs
- Scenario C: Full Migration including upgrade to wcm.io Handler 1.x
Scenario A: Drop-in replacement via Compatibility Layer
Remove these bundles from you deployment:
And instead deploy these bundles:
Existing OSGi configurations for wcm.io Configuration 0.x should work in the same way in the compatibility Layer, the PIDs are unchanged. For configuration persistence, only
io.wcm.config.core.persistence.impl.ToolsConfigPagePersistenceProvider is supported, which still has to be enabled explicitly.
With this change your application should work. Configuration defined via the old wcm.io Configuration SPI are stilled stored together with content in
/tools/config pages. All other configurations managed via the new Sling Context-Aware Configuration API are stored directly in
If you are using AEM Mock-based unit tests in your application together with wcm.io Configuration and wcm.io Handler you have to do the following steps in your Maven poms - remove these dependencies:
And instead add:
Additionally you have to update to the latest AEM Mocks version (1.x for AEM 6.1 or 2.x for AEM 6.2 and up) and remove the following statements from your unit test setup code:
Remove calls to
And instead use the new Mock context plugins like this:
If your are not using wcm.io Handler you can remove
Disable the configuration editor on publish:
Scenario B: Drop-in replacement via Compatibility Layer and update to new APIs
Do the same steps as in Scenario A, but additionally you should update your code:
- Remove all references to deprecated Application API classes and switch to the new ones (see hints in JavaDoc which are the replacements)
If you want to use the new Configuration Annotation Class Feature as described in Apache Sling Context-Aware Configuration you can do this and remove your wcm.io Configuration Parameters Definitions instead. You then use directly the Sling Context-Aware Configuration API to read the configuration data. Within Sightly templates you have to switch the syntax to access the configuration as well as described in the Sling Context-Aware documentation. The configuration of your parameters are then stored in
/conf and no longer in
./tools/config pages. Only the configuration parameters provided by wcm.io Handler still use the compatibility layer. In the configuration editor you can edit both.
Scenario C: Full Migration including upgrade to wcm.io Handler 1.x