I have been working I an migration utility for OpenKM and I performed some changes in jackrabit-core to enable version import, preserving the modification date. Also modified org.apache.jackrabbit.core.NodeImpl to preserve UUID in the migration process.
This migration process is needed because there are changes in repository node definition, and Jackrabbit can't deal with this actually. I've attache a PDF with the changes needed in Jackrabbit-core. It works and there was no problems with the migrated repository. On Thu, Feb 5, 2009 at 3:48 PM, Ivan Latysh <[email protected]> wrote: > Torgeir Veimo wrote: > >>>> I forgot an important question... Does it backup / restore document >>>> version history? >>> >>> That is one major limitation, JCR does not provide an API to manipulate >>> versions. JCR Backup will back up version history, but won't restore it. >>> >>> If you need to backup/restore versions, the only solution is to use DB >>> Persistence and DB backup/restore. >> >> So this tool is not fully usable with versioned content if one need to >> move from one database vendor to another? > > JCR Backup uses JCR API for backup/restore, and does not provide any DB > specific tools. > > -- > Ivan Latysh > [email protected] > -- Paco Avila GIT Consultors tel: +34 971 498310 fax: +34 971496189 e-mail: [email protected] http://www.git.es
