[
https://issues.apache.org/jira/browse/SLING-6788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15982640#comment-15982640
]
Stefan Seifert commented on SLING-6788:
---------------------------------------
good hint - i've added a new section about the "Management API" covering also
this filtering
http://sling.apache.org/documentation/bundles/context-aware-configuration/context-aware-configuration.html#management-api
i also forgot to mention that with this ticket i changed the default filtering
from the list above to all properties within the "jcr:" namespace. but it is
configurable now. in most cases configuration property names will not contain
any namespaces.
> Context-Aware Config: Make filtered property names for configuration
> persistence configurable
> ---------------------------------------------------------------------------------------------
>
> Key: SLING-6788
> URL: https://issues.apache.org/jira/browse/SLING-6788
> Project: Sling
> Issue Type: New Feature
> Components: Extensions
> Affects Versions: Context-Aware Configuration Impl 1.3.2
> Reporter: Stefan Seifert
> Assignee: Stefan Seifert
> Labels: contextaware-config
> Fix For: Context-Aware Configuration Impl 1.4.0
>
>
> currently, a hard-coded list of filtered property names is applied in the
> configuration manager implementation and the default configuration
> persistence implementation:
> {noformat}
> jcr:primaryType
> jcr:mixinTypes
> jcr:created
> jcr:createdBy
> jcr:lastModified
> jcr:lastModifiedBy
> jcr:uuid
> {noformat}
> this list should be made configurable because in upstream applications more
> properties might need to be filtered e.g. to track replication status.
> the possibility to filter a list of property names by name or regex should be
> made accessible in the ConfigurationManager API that is part of the
> Management API so other configuration persistence applications may use it as
> well.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
