On 13/09/16 15:27, "Davide Giannella" <[email protected]> wrote:
>On 12/09/2016 09:48, Stefan Egli wrote: >> IIUC then EventListeners are registered via either JCR's >> ObservationManager or Jackrabbit's extension at [0]. If you want to do >> this in Oak (ie not in Jackrabbit) then would you extend Oak's >> Observationmanager ([1]) directly? >Didn't look at the code and didn't think all the implications. > >Would it be an option to expose, >javax.jcr.oak.observation.OakObservationManager that extends >javax.jcr.observation.ObservationManager in which we expose what need? Right, there's probably two options: # (oak) add another variant of addEventListener to OakObservationManager ([0]) # (jackrabbit) integrate that into the JackrabbitEventFilter ([1]) I guess it comes down to API design and cleanliness, I don't have any preference. Cheers, Stefan -- [0] - https://github.com/apache/jackrabbit-oak/blob/trunk/oak-jcr/src/main/java/o rg/apache/jackrabbit/oak/jcr/observation/ObservationManagerImpl.java#L179 [1] - https://github.com/apache/jackrabbit/blob/trunk/jackrabbit-api/src/main/jav a/org/apache/jackrabbit/api/observation/JackrabbitEventFilter.java
