...
Scenario B: Drop-in replacement via Compatibility Layer and update to new APIs
TBDDo 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
TBD
Related articles
...