...
Full documentation: http://wcm.io/config/
adaptTo() Talk: http://adapt.to/2015/en/schedule/building-aem-applications-with-wcm-io.html
Key features:
- Supports "context-specific" configuration and system-wide configuration
- Supports inheritance of configuration parameter across nested contexts, incl. some control with "locking" inheritance on a certain level
- Provides a simple ValueMap-based API to access configuration values, and a direct mapping to binding variables in Sightly
- Links content subtrees with configuration nodes via pluggable Configuration Finder Strategies
- Storage of configuration is pluggable, storage together with content (in
tools/confignodes) or in a separate/confpath is supported out of the box - Defines an "application" concept to separate different applications with different configuration strategies within a single AEM instance
- wcm.io Configurations are "self-describing" with metadata (name, type, descriptions, default values) which allow GUIs to automatically build nice edit dialogs for them.
- Pluggable Override providers allow to override configuration parameters in certain context/conditions/path e.g. via OSGi config, system environment parameter or request header. Useful for QA/testing purposes.
- Provides a Configuration Management API for building Configuration Management Tools
- Provides a AEM Touch UI Configuration Editor for inspecting and editing configuration parameters and control the inheritance
...