update: content migration for mix:versionable
(MGNLTOOLS-9)
|
|
| Status: | Closed |
| Project: | Repository Tools |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.1 |
| Type: | Sub-task | Priority: | Major |
| Reporter: | Philipp Bärfuss | Assignee: | Jan Haderka |
| Resolution: | Not an issue | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Date of First Response: | |||||||||
| Description |
|
In ContentUpdate.processNode(Content) we use the cr removeMixin() method. While this works the mixin property is not updated (might be a jackrabbit bug). You see that when we print the content: /page/paragraph/jcr:mixinTypes=mix:versionable The value persist no matter whether cleaned up by normal JR API or by PM operations. Further tests revealed value is actually deleted and reappears after restarting repository. This value is also visible only when iterating values of jcr:mixinType property not when looking at node types obtained by getNodeTypes() call. Also second attempt to remove this mixin by using JR API fails with exception indicating no such mixin is defined. |
| Comments |
| Comment by Jan Haderka [ 28/Jul/08 ] |
|
This is caused by bug in JackRabbit see https://issues.apache.org/jira/browse/JCR-1632 for details. |
| Comment by Magnolia International [ 01/Oct/08 ] |
|
not an issue: no resolution -> "close" instead of "resolve" |