On 20.02.2014, at 07:51, Bertrand Delacretaz <bdelacre...@apache.org> wrote:
> Probably not, but if your tool can be made available in the webconsole > when running on Sling, that would make it more integrated than if it's > standalone. The focus should still be on standalone runs - when the "system" is running, there are many jcr browsers already available to do the same. But when it's down, you have nothing atm. I just recently was involved in an outage where something was creating too many temporary content in the repository and it would have been useful to just delete it while the system was down. I guess it's ok if this is on the lower levels on Oak vs. JCR API, as long as it gets the job done efficiently. Should probably warn you about not caring for ACLs etc. - but that's rarely what you want anyway in such an admin-needs-to-fix-it scenario. Cheers, Alex
