-
Bug
-
Resolution: Won't Fix
-
Major
-
None
-
4.0.1
-
None
-
OpenJDK 1.6.0 on CentOS 5.3 64bit with ext3 filesystem, Magnolia OnAir 4.0.1
In situation where it is possible that two same name siblings exist, during activation of these nodes, the MetaData nodes get mixed up between the two nodes (i.e. it seems that the 'first' node gets the content of the 'second' node's MetaData node).
It is possible to reproduce this by importing the attached author-data.rtsi.proxyObjects.2009.04.02.Test-05.xml into the data workspace, and then trying to activate it. The data in the author instance will be ok, but the data in the public instance will be mixed up, about as in the above example.
- is related to
-
MAGNOLIA-2771 activation: children are activated before the parent which causes parent not found exceptions
- Closed
-
MAGNOLIA-5433 As a developer it's clear that I cannot use same name siblings in Magnolia
- Closed
-
MAGNOLIA-2738 Duplicate content and activation problems with DMS & STK
- Closed
-
MGNLACTIVATION-67 Same name siblings
- Closed