If a node is removed and added in one go, resource added event should be fired
------------------------------------------------------------------------------
Key: SLING-2063
URL: https://issues.apache.org/jira/browse/SLING-2063
Project: Sling
Issue Type: Bug
Reporter: Carsten Ziegeler
Assignee: Carsten Ziegeler
If a resource is removed and added in one session operation, the bridge logic
compacts this to a resource remove event and not a resource added event.
For the following set of jcr observation events:
JCR: Event: Path: /content/en/channels/second, NodeRemoved: , UserId: admin,
Timestamp: 1304097112590, UserData: null, Info: {}
JCR: Event: Path: /content/en/channels/second, NodeAdded: , UserId: admin,
Timestamp: 1304097112590, UserData: null, Info: {}
JCR: Event: Path: /content/en/channels/third, NodeRemoved: , UserId: admin,
Timestamp: 1304097112590, UserData: null, Info: {}
JCR: Event: Path: /content/en/channels/third, NodeAdded: , UserId: admin,
Timestamp: 1304097112590, UserData: null, Info: {}
these OSGi resource events are generated:
SLING: path=/content/en/channels/third
topic=org/apache/sling/api/resource/Resource/REMOVED
SLING: path=/content/en/channels/third
topic=org/apache/sling/api/resource/Resource/REMOVED
We should check the order of jcr events when compacting: remove followed by add
is an add, add followed by a remove is a remove
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
