(+gentle bump ;) In JCR-4046 I've now added another example for doing a new event feature in oak-jcr (this time for subtree aggregation).
Wdyt? Should we move forward with suggested EventFilterBuilder approach and skip adding these 5 features to the JackrabbitEventFilter? Cheers, Stefan On 25/10/16 16:15, "Stefan Egli" <[email protected]> wrote: >On 24/10/16 22:27, "Michael Dürig" <[email protected]> wrote: > >>A related question is how we retrofit this to Jackrabbit 2. How do users >>know (and find out) which of these features is supported or not. > >We discussed this offline: what we could do instead of extending the >JackrabbitEventFilter is to introduce a oak-core utility eg >EventFilterBuilder that would take a JackrabbitEventFilter and return a >'modified' filter that contains the extended filter functionality. That >way it would be clear that it's only supported by oak-core. And it would >remove the necessity to extend JackrabbitEventFilter in the first place. > >Added a sketch of how this could look to [0]. > >Wdyt? > >Cheers, >Stefan >-- >[0] - >https://issues.apache.org/jira/browse/JCR-4044?focusedCommentId=15605418&p >a >ge=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#commen >t >-15605418 > >
