Author: sseifert
Date: Thu May 18 11:28:59 2017
New Revision: 1795504
URL: http://svn.apache.org/viewvc?rev=1795504&view=rev
Log:
fix typos
Modified:
sling/site/trunk/content/documentation/bundles/context-aware-configuration/context-aware-configuration.mdtext
Modified:
sling/site/trunk/content/documentation/bundles/context-aware-configuration/context-aware-configuration.mdtext
URL:
http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/bundles/context-aware-configuration/context-aware-configuration.mdtext?rev=1795504&r1=1795503&r2=1795504&view=diff
==============================================================================
---
sling/site/trunk/content/documentation/bundles/context-aware-configuration/context-aware-configuration.mdtext
(original)
+++
sling/site/trunk/content/documentation/bundles/context-aware-configuration/context-aware-configuration.mdtext
Thu May 18 11:28:59 2017
@@ -231,7 +231,7 @@ The Context-Aware Configuration Implemen
The main entry point is the OSGi service
`org.apache.sling.caconfig.management.ConfigurationManager`. It allows to get,
write or delete singleton configurations and configuration lists. Configuration
data is returned using `ConfigurationData` and `ConfigurationCollectionData`
objects which also provide access to additional metadata about the resolving
process and inheritance/override status of each property. Internally the
configuration manager uses the [SPI][spi] implementation to resolve and write
the configuration data.
-Whenever configuration data is read or written from the configuration
resources a filtering of property names is applied to make sure
"system-properties" like `jcr:primaryType` or 'jcr:created' are not returned as
part of the configuration data. A list of regular expressions for this
filtering can be configured via the "Apache Sling Context-Aware Configuration
Management Settings" OSGi configuration. The configuration is accessible to
custom persistence implementations via the
`org.apache.sling.caconfig.management.ConfigurationManagementSettings` OSGi
service. By default all properties in the `jcr:` namespace are filtered out.
+Whenever configuration data is read or written from the configuration
resources a filtering of property names is applied to make sure "system
properties" like `jcr:primaryType` or `jcr:created` are not returned as part of
the configuration data. A list of regular expressions for this filtering can be
configured via the "Apache Sling Context-Aware Configuration Management
Settings" OSGi configuration. The configuration is accessible to custom
persistence implementations via the
`org.apache.sling.caconfig.management.ConfigurationManagementSettings` OSGi
service. By default all properties in the `jcr:` namespace are filtered out.
# References
