You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Michael Daglian (JIRA)" <ji...@apache.org> on 2005/07/07 18:32:26 UTC
[jira] Created: (JCR-166) Versioned node importXML fails
Versioned node importXML fails
------------------------------
Key: JCR-166
URL: http://issues.apache.org/jira/browse/JCR-166
Project: Jackrabbit
Type: Bug
Components: versioning
Reporter: Michael Daglian
Attachments: output.log, testrepository.xml
When importing system-view XML previously exported for a repository, any nodes with a version history cannot be reimported. This appears to be due to the version manager attempting to create a new version history for the node, which fails due to a previous history existing for the same UUID. The behavior occurs with ImportUUIDBehavior.IMPORT_UUID_COLLISION_REPLACE_EXISTING and ImportUUIDBehavior.IMPORT_UUID_COLLISION_REMOVE_EXISTING, with the following stack trace:
javax.jcr.version.VersionException: History already exists for node a892651d-1688-46cd-bb12-14f2f0b3d886
at org.apache.jackrabbit.core.version.VersionManagerImpl.createVersionHistory(VersionManagerImpl.java:194)
at org.apache.jackrabbit.core.ItemImpl.initVersionHistories(ItemImpl.java:900)
at org.apache.jackrabbit.core.ItemImpl.save(ItemImpl.java:1313)
at org.apache.jackrabbit.core.SessionImpl.save(SessionImpl.java:766)
I am using the 1.0-dev version, revision 209290 obtained on 05 Jul, 2005 at 9:18:02 EST. Attached please find my repository configuration and the test code. Thanks!
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (JCR-166) Versioned node importXML fails
Posted by "Michael Daglian (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-166?page=all ]
Michael Daglian updated JCR-166:
--------------------------------
Attachment: output.log
> Versioned node importXML fails
> ------------------------------
>
> Key: JCR-166
> URL: http://issues.apache.org/jira/browse/JCR-166
> Project: Jackrabbit
> Type: Bug
> Components: versioning
> Reporter: Michael Daglian
> Attachments: output.log, testrepository.xml
>
> When importing system-view XML previously exported for a repository, any nodes with a version history cannot be reimported. This appears to be due to the version manager attempting to create a new version history for the node, which fails due to a previous history existing for the same UUID. The behavior occurs with ImportUUIDBehavior.IMPORT_UUID_COLLISION_REPLACE_EXISTING and ImportUUIDBehavior.IMPORT_UUID_COLLISION_REMOVE_EXISTING, with the following stack trace:
> javax.jcr.version.VersionException: History already exists for node a892651d-1688-46cd-bb12-14f2f0b3d886
> at org.apache.jackrabbit.core.version.VersionManagerImpl.createVersionHistory(VersionManagerImpl.java:194)
> at org.apache.jackrabbit.core.ItemImpl.initVersionHistories(ItemImpl.java:900)
> at org.apache.jackrabbit.core.ItemImpl.save(ItemImpl.java:1313)
> at org.apache.jackrabbit.core.SessionImpl.save(SessionImpl.java:766)
> I am using the 1.0-dev version, revision 209290 obtained on 05 Jul, 2005 at 9:18:02 EST. Attached please find my repository configuration and the test code. Thanks!
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (JCR-166) Versioned node importXML fails
Posted by "Michael Daglian (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-166?page=all ]
Michael Daglian updated JCR-166:
--------------------------------
Attachment: JCRVersionTest.java
> Versioned node importXML fails
> ------------------------------
>
> Key: JCR-166
> URL: http://issues.apache.org/jira/browse/JCR-166
> Project: Jackrabbit
> Type: Bug
> Components: versioning
> Reporter: Michael Daglian
> Attachments: JCRVersionTest.java, output.log, testrepository.xml
>
> When importing system-view XML previously exported for a repository, any nodes with a version history cannot be reimported. This appears to be due to the version manager attempting to create a new version history for the node, which fails due to a previous history existing for the same UUID. The behavior occurs with ImportUUIDBehavior.IMPORT_UUID_COLLISION_REPLACE_EXISTING and ImportUUIDBehavior.IMPORT_UUID_COLLISION_REMOVE_EXISTING, with the following stack trace:
> javax.jcr.version.VersionException: History already exists for node a892651d-1688-46cd-bb12-14f2f0b3d886
> at org.apache.jackrabbit.core.version.VersionManagerImpl.createVersionHistory(VersionManagerImpl.java:194)
> at org.apache.jackrabbit.core.ItemImpl.initVersionHistories(ItemImpl.java:900)
> at org.apache.jackrabbit.core.ItemImpl.save(ItemImpl.java:1313)
> at org.apache.jackrabbit.core.SessionImpl.save(SessionImpl.java:766)
> I am using the 1.0-dev version, revision 209290 obtained on 05 Jul, 2005 at 9:18:02 EST. Attached please find my repository configuration and the test code. Thanks!
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Closed: (JCR-166) Versioned node importXML fails
Posted by "Stefan Guggisberg (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-166?page=all ]
Stefan Guggisberg closed JCR-166:
---------------------------------
Fix Version: 1.0
Resolution: Fixed
fixed in SVN rev. 209776
> Versioned node importXML fails
> ------------------------------
>
> Key: JCR-166
> URL: http://issues.apache.org/jira/browse/JCR-166
> Project: Jackrabbit
> Type: Bug
> Components: versioning
> Reporter: Michael Daglian
> Assignee: Stefan Guggisberg
> Fix For: 1.0
> Attachments: JCRVersionTest.java, output.log, testrepository.xml
>
> When importing system-view XML previously exported for a repository, any nodes with a version history cannot be reimported. This appears to be due to the version manager attempting to create a new version history for the node, which fails due to a previous history existing for the same UUID. The behavior occurs with ImportUUIDBehavior.IMPORT_UUID_COLLISION_REPLACE_EXISTING and ImportUUIDBehavior.IMPORT_UUID_COLLISION_REMOVE_EXISTING, with the following stack trace:
> javax.jcr.version.VersionException: History already exists for node a892651d-1688-46cd-bb12-14f2f0b3d886
> at org.apache.jackrabbit.core.version.VersionManagerImpl.createVersionHistory(VersionManagerImpl.java:194)
> at org.apache.jackrabbit.core.ItemImpl.initVersionHistories(ItemImpl.java:900)
> at org.apache.jackrabbit.core.ItemImpl.save(ItemImpl.java:1313)
> at org.apache.jackrabbit.core.SessionImpl.save(SessionImpl.java:766)
> I am using the 1.0-dev version, revision 209290 obtained on 05 Jul, 2005 at 9:18:02 EST. Attached please find my repository configuration and the test code. Thanks!
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (JCR-166) Versioned node importXML fails
Posted by "Michael Daglian (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-166?page=comments#action_12315256 ]
Michael Daglian commented on JCR-166:
-------------------------------------
Code to be added quite soon. Just need to remove some proprietary pieces.
> Versioned node importXML fails
> ------------------------------
>
> Key: JCR-166
> URL: http://issues.apache.org/jira/browse/JCR-166
> Project: Jackrabbit
> Type: Bug
> Components: versioning
> Reporter: Michael Daglian
> Attachments: output.log, testrepository.xml
>
> When importing system-view XML previously exported for a repository, any nodes with a version history cannot be reimported. This appears to be due to the version manager attempting to create a new version history for the node, which fails due to a previous history existing for the same UUID. The behavior occurs with ImportUUIDBehavior.IMPORT_UUID_COLLISION_REPLACE_EXISTING and ImportUUIDBehavior.IMPORT_UUID_COLLISION_REMOVE_EXISTING, with the following stack trace:
> javax.jcr.version.VersionException: History already exists for node a892651d-1688-46cd-bb12-14f2f0b3d886
> at org.apache.jackrabbit.core.version.VersionManagerImpl.createVersionHistory(VersionManagerImpl.java:194)
> at org.apache.jackrabbit.core.ItemImpl.initVersionHistories(ItemImpl.java:900)
> at org.apache.jackrabbit.core.ItemImpl.save(ItemImpl.java:1313)
> at org.apache.jackrabbit.core.SessionImpl.save(SessionImpl.java:766)
> I am using the 1.0-dev version, revision 209290 obtained on 05 Jul, 2005 at 9:18:02 EST. Attached please find my repository configuration and the test code. Thanks!
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (JCR-166) Versioned node importXML fails
Posted by "Michael Daglian (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-166?page=all ]
Michael Daglian updated JCR-166:
--------------------------------
Attachment: testrepository.xml
> Versioned node importXML fails
> ------------------------------
>
> Key: JCR-166
> URL: http://issues.apache.org/jira/browse/JCR-166
> Project: Jackrabbit
> Type: Bug
> Components: versioning
> Reporter: Michael Daglian
> Attachments: output.log, testrepository.xml
>
> When importing system-view XML previously exported for a repository, any nodes with a version history cannot be reimported. This appears to be due to the version manager attempting to create a new version history for the node, which fails due to a previous history existing for the same UUID. The behavior occurs with ImportUUIDBehavior.IMPORT_UUID_COLLISION_REPLACE_EXISTING and ImportUUIDBehavior.IMPORT_UUID_COLLISION_REMOVE_EXISTING, with the following stack trace:
> javax.jcr.version.VersionException: History already exists for node a892651d-1688-46cd-bb12-14f2f0b3d886
> at org.apache.jackrabbit.core.version.VersionManagerImpl.createVersionHistory(VersionManagerImpl.java:194)
> at org.apache.jackrabbit.core.ItemImpl.initVersionHistories(ItemImpl.java:900)
> at org.apache.jackrabbit.core.ItemImpl.save(ItemImpl.java:1313)
> at org.apache.jackrabbit.core.SessionImpl.save(SessionImpl.java:766)
> I am using the 1.0-dev version, revision 209290 obtained on 05 Jul, 2005 at 9:18:02 EST. Attached please find my repository configuration and the test code. Thanks!
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Assigned: (JCR-166) Versioned node importXML fails
Posted by "Stefan Guggisberg (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-166?page=all ]
Stefan Guggisberg reassigned JCR-166:
-------------------------------------
Assign To: Stefan Guggisberg
> Versioned node importXML fails
> ------------------------------
>
> Key: JCR-166
> URL: http://issues.apache.org/jira/browse/JCR-166
> Project: Jackrabbit
> Type: Bug
> Components: versioning
> Reporter: Michael Daglian
> Assignee: Stefan Guggisberg
> Attachments: JCRVersionTest.java, output.log, testrepository.xml
>
> When importing system-view XML previously exported for a repository, any nodes with a version history cannot be reimported. This appears to be due to the version manager attempting to create a new version history for the node, which fails due to a previous history existing for the same UUID. The behavior occurs with ImportUUIDBehavior.IMPORT_UUID_COLLISION_REPLACE_EXISTING and ImportUUIDBehavior.IMPORT_UUID_COLLISION_REMOVE_EXISTING, with the following stack trace:
> javax.jcr.version.VersionException: History already exists for node a892651d-1688-46cd-bb12-14f2f0b3d886
> at org.apache.jackrabbit.core.version.VersionManagerImpl.createVersionHistory(VersionManagerImpl.java:194)
> at org.apache.jackrabbit.core.ItemImpl.initVersionHistories(ItemImpl.java:900)
> at org.apache.jackrabbit.core.ItemImpl.save(ItemImpl.java:1313)
> at org.apache.jackrabbit.core.SessionImpl.save(SessionImpl.java:766)
> I am using the 1.0-dev version, revision 209290 obtained on 05 Jul, 2005 at 9:18:02 EST. Attached please find my repository configuration and the test code. Thanks!
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira