[ http://issues.apache.org/jira/browse/JCR-236?page=comments#action_12331893 ]
Stefan Guggisberg commented on JCR-236: --------------------------------------- i was unable to reproduce the described behaviour. i exported a versionable node with Session.exportSystemView(...) and re-imported it using Workspace.importXML(..., IMPORT_UUID_CREATE_NEW) at a different path. i verified that the new node had a new version history and that i could successfully perform versioning operations on it. please provide detailed instructions on how this bug can be reproduced (a small code fragment would be ideal). > Jackrabbit respects the property semantics (7.3.3 spec) but it doesn't create > the versionhistory for imported nodes with new uuids > ---------------------------------------------------------------------------------------------------------------------------------- > > Key: JCR-236 > URL: http://issues.apache.org/jira/browse/JCR-236 > Project: Jackrabbit > Type: Bug > Components: versioning > Reporter: Edgar Poce > Assignee: Stefan Guggisberg > Priority: Minor > Fix For: 1.0 > > when a versioned node is imported to the workspace the versionable mixin type > is respected but no versionhistory is created for nodes with new uuids. As a > consequence the imported nodes are inconsistent, and jackrabbit throws an > ItemNotFoundException when trying to perform any versioning operation. -- 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
