You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2012/11/30 16:57:58 UTC
[jira] [Created] (SLING-2688) Node remove/add events should not be
compacted
Carsten Ziegeler created SLING-2688:
---------------------------------------
Summary: Node remove/add events should not be compacted
Key: SLING-2688
URL: https://issues.apache.org/jira/browse/SLING-2688
Project: Sling
Issue Type: Improvement
Components: JCR
Affects Versions: JCR Resource 2.2.0
Reporter: Carsten Ziegeler
Assignee: Carsten Ziegeler
Fix For: JCR Resource 2.2.2
When a node is removed and added within the same save operation, this results in the following jcr events:
- node removed
- node added
- property added for each property
Right now this is compacted into a resource updated event with the newly set properties.
However, if the node has a property before it's removed which is not being readded, the sent OSGi events do not cover this change, as just an updated resource event with the new properties is sent. So a listener might not be aware that a property is removed.
Therefore we should sent separate events.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (SLING-2688) Node remove/add events should not be
compacted
Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-2688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler resolved SLING-2688.
-------------------------------------
Resolution: Fixed
> Node remove/add events should not be compacted
> ----------------------------------------------
>
> Key: SLING-2688
> URL: https://issues.apache.org/jira/browse/SLING-2688
> Project: Sling
> Issue Type: Improvement
> Components: JCR
> Affects Versions: JCR Resource 2.2.0
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: JCR Resource 2.2.2
>
>
> When a node is removed and added within the same save operation, this results in the following jcr events:
> - node removed
> - node added
> - property added for each property
> Right now this is compacted into a resource updated event with the newly set properties.
> However, if the node has a property before it's removed which is not being readded, the sent OSGi events do not cover this change, as just an updated resource event with the new properties is sent. So a listener might not be aware that a property is removed.
> Therefore we should sent separate events.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira