[MAGNOLIA-3481] ContentUtil: copyInSession fails if source and target are siblings Created: 22/Dec/10 Updated: 03/Dec/13 Resolved: 03/Dec/13 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | 4.4 |
| Fix Version/s: | 5.2 |
| Type: | Bug | Priority: | Major |
| Reporter: | Philipp Bärfuss | Assignee: | Unassigned |
| Resolution: | Outdated | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| 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 |
|
To implement the copy in session we use JCR export and import. The renaming of the node is only done after the import. If the import is performed under the same parent node the name after the import is most likely name[1] but there is no guarantee for that. Consequently we have to rename the node in the file we are going to import, respectively manipulating the SAX events. |
| Comments |
| Comment by Philipp Bärfuss [ 18/Jan/11 ] |
|
We are finalizing 4.4.2 hence I am moving this issue to 4.4.3. |
| Comment by Philipp Bärfuss [ 03/Dec/13 ] |
|
Since 5.2 we don't allow same name siblings anymore as they are not supported by the activation. The ContentUtil has been improved but we don't plan to backport this change. |