Hi Davide, On 08/09/16 14:24, "Davide Giannella" <[email protected]> wrote:
>On 07/09/2016 14:04, Michael Dürig wrote: >> No not open them. But make their functionality available through an >> API. Since JCR is dead (hint hint) we probably have to come up with an >> ad-hoc API here. >FWIW, I'm for exposing this aspect as Oak API. Would be fine for me, however, how would you do that? 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? Cheers, Stefan -- [0] - https://github.com/apache/jackrabbit/blob/trunk/jackrabbit-api/src/main/jav a/org/apache/jackrabbit/api/observation/JackrabbitObservationManager.java#L 26 [1] - https://github.com/apache/jackrabbit-oak/blob/trunk/oak-jcr/src/main/java/o rg/apache/jackrabbit/oak/jcr/observation/ObservationManagerImpl.java > >Then in Oak we implement few Filters for the already existing mechanism, >so that the jcr layer can map the JCR API as Oak api. > >An application that needs to have complex filtering, will have to >leverage the Oak API. > >Don't know whether it will be possible for an application to leverage >*both* JCR and Oak APIs but I'm sure there are ways around it. > >Cheers >Davide > >
