[
https://issues.apache.org/jira/browse/JCRVLT-390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Om updated JCRVLT-390:
----------------------
Description:
We have a use case where the replication agent's *enabled* flag should not be
overwritten with every deployment.
Referring to the comment here
https://issues.apache.org/jira/browse/JCRVLT-120?focusedCommentId=16907459&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16907459
and the documentation for Property Filtering on
[https://jackrabbit.apache.org/filevault/filter.html] , I am trying to
implement this
{code:java}
<filter root="/etc/replication/agents.author/some-data-exporter">
<include pattern="/etc/replication/agents.author/some-data-exporter/.*"/>
<exclude pattern=".*/enabled" matchProperties="true"/>
</filter>
{code}
But when I deploy the package using this filter definition, the exclude pattern
is not applied. Ideally this should include everything below the specified
path and just ignore the property enabled in the existing content. But this is
not happening as the whole content is replaced.
We are using this in AEM with the version
3.2.8([org.apache.jackrabbit.vault|http://localhost:4502/system/console/bundles/150])
the Node structure is:
+/etc/replication/agents.author/some-data-exporter
+ jcr:content/
- enabled="true"
- property1="some value"
- property2="some other value"
was:
We have a use case where the replication agent's *enabled* flag should not be
overwritten with every deployment.
Referring to the comment here
https://issues.apache.org/jira/browse/JCRVLT-120?focusedCommentId=16907459&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16907459
and the documentation for Property Filtering on
[https://jackrabbit.apache.org/filevault/filter.html] , I am trying to
implement this
{code:java}
<filter root="/etc/replication/agents.author/some-data-exporter">
<include pattern="/etc/replication/agents.author/some-data-exporter/.*"/>
<exclude pattern=".*/enabled" matchProperties="true"/>
</filter>
{code}
But when I deploy the package using this filter definition, the exclude pattern
is not applied. Ideally this should include everything below the specified
path and just ignore the property enabled in the existing content. But this is
not happening as the whole content is replaced.
We are using this in AEM with the version
3.2.8([org.apache.jackrabbit.vault|http://localhost:4502/system/console/bundles/150])
> filter based on content properties is not working
> -------------------------------------------------
>
> Key: JCRVLT-390
> URL: https://issues.apache.org/jira/browse/JCRVLT-390
> Project: Jackrabbit FileVault
> Issue Type: Bug
> Components: vlt
> Affects Versions: 3.2.8
> Reporter: Om
> Priority: Minor
>
> We have a use case where the replication agent's *enabled* flag should not be
> overwritten with every deployment.
> Referring to the comment here
> https://issues.apache.org/jira/browse/JCRVLT-120?focusedCommentId=16907459&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16907459
> and the documentation for Property Filtering on
> [https://jackrabbit.apache.org/filevault/filter.html] , I am trying to
> implement this
> {code:java}
> <filter root="/etc/replication/agents.author/some-data-exporter">
> <include pattern="/etc/replication/agents.author/some-data-exporter/.*"/>
> <exclude pattern=".*/enabled" matchProperties="true"/>
> </filter>
> {code}
> But when I deploy the package using this filter definition, the exclude
> pattern is not applied. Ideally this should include everything below the
> specified path and just ignore the property enabled in the existing content.
> But this is not happening as the whole content is replaced.
>
> We are using this in AEM with the version
> 3.2.8([org.apache.jackrabbit.vault|http://localhost:4502/system/console/bundles/150])
>
> the Node structure is:
>
> +/etc/replication/agents.author/some-data-exporter
> + jcr:content/
> - enabled="true"
> - property1="some value"
> - property2="some other value"
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
