History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: NXP-1522
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Dragos Mihalache
Reporter: Florent Guillaume
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Google issue summary
Nuxeo Enterprise Platform

Can't restore some node structures with custom versioning

Created: 04/09/07 21:35   Updated: 27/09/07 18:24
Component/s: JCRConnector
Affects Version/s: 5.1.0.GA
Fix Version/s: 5.1.2

Time Tracking:
Not Specified

Resolution Date: 27/09/07 18:24
Require Callback: No
Participants: Dragos Mihalache and Florent Guillaume
Date of First Response: 27/09/07 18:24
Tags:


 Description  « Hide
Some node structures can't be restored properly, producing:

javax.jcr.nodetype.ConstraintViolationException: no matching property definition found for {http://www.nuxeo.org/ecm/system}frozenNode
        at org.apache.jackrabbit.core.nodetype.EffectiveNodeType.getApplicablePropertyDef(EffectiveNodeType.java:773)
        at org.apache.jackrabbit.core.NodeImpl.getApplicablePropertyDefinition(NodeImpl.java:933)
        at org.apache.jackrabbit.core.NodeImpl.getOrCreateProperty(NodeImpl.java:429)
        at org.apache.jackrabbit.core.NodeImpl.getOrCreateProperty(NodeImpl.java:400)
        at org.apache.jackrabbit.core.NodeImpl.setProperty(NodeImpl.java:2232)
        at org.nuxeo.ecm.core.versioning.custom.VerServUtils.restoreNodeProps(VerServUtils.java:514)
        at org.nuxeo.ecm.core.versioning.custom.VerServUtils.restoreChildNodes(VerServUtils.java:604)
        at org.nuxeo.ecm.core.versioning.custom.VerServUtils.restoreNodeProps(VerServUtils.java:526)
        at org.nuxeo.ecm.core.versioning.custom.CustomVersioningService.restore(CustomVersioningService.java:312)



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Florent Guillaume - 04/09/07 21:35
Awaiting actual info about the node structure from the developer having the error.


Florent Guillaume - 05/09/07 11:39
Apparently the problematic node is a node of type ecmnt:container, which is consistent with the developer trying to restore folderish nodes (without touching the children).



Dragos Mihalache - 27/09/07 18:24
the frozenNode property should be set only for the document node and skipped while recursively copying children nodes props.