Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
Content Distribution Core 0.1.18
-
None
Description
JcrEventTrigger aggregates generated DistributionRequests in order to mitigate the risk of having badly ordered events result in distributions that may lead to unconsistent state of the receiving instance.
In case 2 nodes one of which is descendant of the others get aggregated in the same request the resulting package will only include siblings of the deep path with its names, not their properties, resulting in removing existing properties by the deep node's siblings on the receiving side.
I am not 100% sure this is a desired behaviour in FileVault, however since this may also affect custom serializers I think the right fix is to add the siblings's paths to such distribution requests.