jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-1972) Preserving UUID and document version history on repository migration
Date Tue, 14 Jul 2009 12:41:14 GMT

    [ https://issues.apache.org/jira/browse/JCR-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12730818#action_12730818
] 

Jukka Zitting commented on JCR-1972:
------------------------------------

The patch is creating lots of duplicate code in the extra methods. Can we avoid that?

Also, it would be good to have a check to prevent someone to add a new node with an id that
already exists in the workspace.

> Preserving UUID and document version history on repository migration
> --------------------------------------------------------------------
>
>                 Key: JCR-1972
>                 URL: https://issues.apache.org/jira/browse/JCR-1972
>             Project: Jackrabbit Content Repository
>          Issue Type: Wish
>          Components: jackrabbit-core
>    Affects Versions: core 1.4.8
>            Reporter: Paco Avila
>         Attachments: Jackrabbit_modifications.pdf, JCR-1972.patch, JCR-1972_1.x.patch
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message