[
https://issues.apache.org/jira/browse/JCRVLT-787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17951030#comment-17951030
]
Julian Reschke commented on JCRVLT-787:
---------------------------------------
[~joerghoh]...:
1. Deleting a tree is a single JCR method call; so by default we do not know
how many child nodes are affected. Unless I'm missing something, the caller
would need to do the recursion itself. That might have undesirable performance
effects.
2. Isn't it already possible to use a custom progress listener?
> package installation should provide metrics
> -------------------------------------------
>
> Key: JCRVLT-787
> URL: https://issues.apache.org/jira/browse/JCRVLT-787
> Project: Jackrabbit FileVault
> Issue Type: Improvement
> Components: Packaging
> Affects Versions: 3.8.2
> Reporter: Joerg Hoh
> Priority: Major
>
> We recently had an issue that the installation of a content package caused
> the deletion of a large content subtree; while the package worked as it
> should , installing the package was neither expected nor known.
> For that reason we just saw the result and it took a while to identify the
> package installation as the root-cause of this situation. This was
> complicated by the lack of know-how and familiarity of the investigating
> people with filevault and content packages.
> For that reason it would be great if filevault could provide a collection of
> metrics (nodes added, nodes deleted, etc) when a package has been
> successfully installed.
> In this case the situation was like this: The filter.xml contained a rule for
> /content/foobar with no mode specified (so the default value of REPLACE was
> used), and in the package just a .content.xml for /content/foobar was
> included; that wiped the entire subtree (a few thousand nodes) in the
> repository below /content/foobar.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
