[
https://issues.apache.org/jira/browse/JCRVLT-120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15395797#comment-15395797
]
Timothee Maret commented on JCRVLT-120:
---------------------------------------
AFAIU from looking at the filevault code, this could be implemented by an
implementation of {{o.a.j.v.f.a.Aggregator}}.
It may make sense to add this feature to the aggregators in filevault (I guess
in {{FileFolderAggregator}} and {{RootAggregator}}). However, the
{{ExportOptions}} should likely be extended in order to allow providing the
list of properties to filter.
Alternatively, I think we could let the user to create its own aggregator and
adds it in the list of {{Aggregator}} provided in the {{VaultFsConfig}}
instance provided in the {{o.a.j.v.p.ExportOptions}} passed through the
{{o.a.j.v.p.PackageManager#assemble}} method. This would require either
modifying the {{AggregateManagerImpl}} such that it _merges_ the
{{VaultFsConfig}} with the default one, or allowing the filevault consumer to
build the default {{VaultFsConfig}} instance.
[~tripod] wdyt ?
> Allow to filter content properties based on property name and value
> --------------------------------------------------------------------
>
> Key: JCRVLT-120
> URL: https://issues.apache.org/jira/browse/JCRVLT-120
> Project: Jackrabbit FileVault
> Issue Type: Improvement
> Components: vlt
> Affects Versions: 3.1.26
> Reporter: Timothee Maret
>
> In our use case, we need to filter content distributed by filevault for
> properties {{cq:lastReplicated}}, {{cq:lastReplicatedBy}} and
> {{cq:lastReplicationAction}}.
> This feature could cover more than those three property and instead be
> generalised to filter any property which name and value match the configured
> filter.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
