[MAGNOLIA-2717] CopyUtil not able to restore versioned nodes with jcr:isCheckedOut property without value Created: 06/May/09  Updated: 23/Jan/13  Resolved: 11/May/09

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: 4.0.1, 3.6.5
Fix Version/s: 4.1, 4.0.2

Type: Bug Priority: Major
Reporter: Jan Haderka Assignee: Jan Haderka
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
relation
is related to MAGNOLIA-2006 Jackrabbit 1.4 support Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled

 Description   

Since fixing JCR-1272 the exception thrown when attempting to restore certain properties have changed. This issue was fixed in JR 1.4, hence any version of Magnolia using JR 1.4 or higher is affected.
The change was necessary to tackle the concurrency issues in JR, but broke the exception handling in CopyUtils while attempting to restore the properties. When versioning nodes, it is possible that subnodes versioned together with the parent end up with jcr:isCheckedOut property with (or without) value. While prior to JR 1.4 attempt to restore such property ended up with ConstrainViolationException which is silently ignored by CopyUtil, now this doesn't work any longer as the RepositoryException is thrown when property with no value is found.



 Comments   
Comment by Jan Haderka [ 11/May/09 ]

Done as of r24826 on trunk and as of r24910 on 4.0 branch.

Generated at Mon Feb 12 03:39:25 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.