Issue Details (XML | Word | Printable)

Key: JCR-535
Type: Improvement Improvement
Status: Closed Closed
Resolution: Won't Fix
Priority: Minor Minor
Assignee: Jukka Zitting
Reporter: Nicolas Toper
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Jackrabbit Content Repository

Ignore root node when importing through sysView

Created: 08/Aug/06 10:17 PM   Updated: 14/Jul/09 03:47 PM
Return to search
Component/s: jackrabbit-core
Affects Version/s: None
Fix Version/s: None

Time Tracking:
Not Specified

File Attachments:
  File Name Date Attached Attached By Size
Text File patch-1-Ignore-root-node.txt 2006-08-08 10:17 PM Nicolas Toper 1.0 kB
Text File Licensed for inclusion in ASF works patch-WorkspaceImporter-231006-2.txt 2006-10-23 10:45 PM Nicolas Toper 3 kB
Text File Licensed for inclusion in ASF works patch-WorkspaceImporter-231006.txt 2006-10-23 06:40 PM Nicolas Toper 10 kB
Text File Licensed for inclusion in ASF works patch-WorkspaceImporterTest-231006.txt 2006-10-23 10:46 PM Nicolas Toper 5 kB
Text File Licensed for inclusion in ASF works WorkspaceImporterRootNodeTest.patch 2006-11-19 02:04 PM Nicolas Toper 5 kB
Issue Links:
Reference
 

Resolution Date: 08/Jul/09 11:42 AM


 Description  « Hide
When importing through a sysView, we should ignore the root node. It is in the sysView to provide a root XML node, but the importer is going to attach it to the repository"s root node... Which would create another root node and often raise exception. This is a know issue

I needed this behavior to change for the backup tool, since I use the sysView. Therefore, I havce slightly updated the WorkspaceImporter. Maybe I should update too the SessionImporter so we have a consistant behavior. What do you think?

 All   Comments   Work Log   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Stefan Guggisberg made changes - 09/Aug/06 09:30 AM
Field Original Value New Value
Link This issue relates to JCR-323 [ JCR-323 ]
Stefan Guggisberg made changes - 09/Aug/06 09:52 AM
Comment [ > I don't think we currently implement the IMPORT_UUID_REPLACE_EXISTING behaviour
> for jcr:root as specified in section 7.3.8. Implementing that would solve Nicolas' problem
> in a standards compliant manner.

no, it wouldn't. we deliberatly don't allow to replace the root node. /jcr:system e.g. is protected,
and for a good reason so because it's system managed and not user editable.

the importXML methods were never intended to serve as restore operations for system managed
data. ]
Nicolas Toper made changes - 23/Oct/06 06:40 PM
Attachment patch-WorkspaceImporter-231006.txt [ 12343446 ]
Nicolas Toper made changes - 23/Oct/06 10:45 PM
Attachment patch-WorkspaceImporter-231006-2.txt [ 12343466 ]
Nicolas Toper made changes - 23/Oct/06 10:46 PM
Attachment patch-WorkspaceImporterTest-231006.txt [ 12343467 ]
Nicolas Toper made changes - 19/Nov/06 02:04 PM
Attachment WorkspaceImporterRootNodeTest.patch [ 12345305 ]
Jukka Zitting made changes - 07/Jul/09 01:00 PM
Workflow jira [ 12381343 ] no-reopen-closed, patch-avail [ 12467953 ]
Jukka Zitting made changes - 08/Jul/09 09:47 AM
Status Open [ 1 ] Patch Available [ 10002 ]
Jukka Zitting made changes - 08/Jul/09 11:42 AM
Resolution Won't Fix [ 2 ]
Assignee Jukka Zitting [ jukkaz ]
Status Patch Available [ 10002 ] Resolved [ 5 ]
Jukka Zitting made changes - 14/Jul/09 03:47 PM
Status Resolved [ 5 ] Closed [ 6 ]

Powered by a free Atlassian JIRA open source license for Apache Software Foundation. Try JIRA - bug tracking software for your team.
Atlassian JIRA the Professional Issue Tracker. (Enterprise Edition, Version: 3.13.2-#335) - Bug/feature request - Atlassian news - Contact Administrators