Hi Alex I had the same requirement recently and developed a small tool[0] that works on Jackrabbit 2's PersistenceManager API. Not having all the JCR layers active speeds up deletes quite a bit.
So I agree, there definitely is a requirement for offline content inspection and manipulation. Regards Julian [0] https://github.com/code-distillery/jackrabbit-pm-tools On Thu, Feb 20, 2014 at 5:13 PM, Alexander Klimetschek <[email protected]> wrote: > On 20.02.2014, at 07:51, Bertrand Delacretaz <[email protected]> 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
