Hi Dominique, I agree on this. But I don't see any other alternative than the one Toby described: add an import/export method to the VersionManager and this means integrating the backup tool to the core which is something we didn't want to do at first.
You raise an interesting question about the storage format reliability (in the "aging" sense). It is one of the main reason why I used the sysView for workspace and versioning backup. It is a reliable format since it is specified in JCR. The specification also specifies the /jcr:system/jcr:versionStorage tree so we will always have a sysView of those resources. It allowed us to piggyback on a working, reliable and implemented format. I propose to stick with this format for now and rediscuss this point when we will be thinking of the version 2 of this tool (quite soon). Cheers Nico my blog! http://www.deviant-abstraction.net !! On 8/17/06, Dominique Pfister <[EMAIL PROTECTED]> wrote:
Hi Nicolas, as Tobi pointed out, I would not rely on the fact that the VersionManager currently uses a PersistenceManager. This could very easily change in the future. Since sysview importing puts restrictions on the items being imported, I'd rather take a low level approach à la o.a.j.c.BatchedItemOperations and use some custom format when importing/exporting items. Cheers Dominique
