[
https://issues.apache.org/jira/browse/SLING-5163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14982678#comment-14982678
]
Carsten Ziegeler commented on SLING-5163:
-----------------------------------------
I think this patch needs to be adjusted, I've changed the API a little bit.
I've also added an additional check to the Jcr/Oak listener as part of
SLING-2784.
I think - although it's code duplication - we should keep the JCR and Oak
listeners as is and maybe provide a switch for either using observation api or
OSGi events.
For the implementation of the observation api, I think we can solely base this
on OAK. All these optimizations make only sense if we can use the Oak api.
While this ties us to the Oak API, I don't think that's problematic as there is
no other implementation used with Sling
> Rewrite the JCR Resource to post events using the new observation API
> ---------------------------------------------------------------------
>
> Key: SLING-5163
> URL: https://issues.apache.org/jira/browse/SLING-5163
> Project: Sling
> Issue Type: Sub-task
> Components: JCR
> Reporter: Tomek Rękawek
> Fix For: JCR Resource 2.6.0
>
> Attachments: SLING-5163.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
