[
https://issues.apache.org/jira/browse/OAK-5013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Egli updated OAK-5013:
-----------------------------
Attachment: OAK-5013.patch
Attached [^OAK-5013.patch] shows a static factory and an abstract base class
{{OakEventFilter}} which could serve as an API. Later changes to the
{{OakEventFilter}} could then be done in a way that existing client code would
not have to be touched ("@ProviderType")
> Introduce observation filter extension mechanism to Oak
> -------------------------------------------------------
>
> Key: OAK-5013
> URL: https://issues.apache.org/jira/browse/OAK-5013
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: jcr
> Affects Versions: 1.5.12
> Reporter: Stefan Egli
> Assignee: Stefan Egli
> Attachments: OAK-5013.patch
>
>
> During [discussions|http://markmail.org/thread/fyngo4dwb7fvlqdj] regarding
> extending JackrabbitEventFilter an interesting suggestion by [~mduerig] came
> up that we could extend the JackrabbitEventFilter in oak explicitly, rather
> than modifying it in Jackrabbit each time we add something oak-specific.
> We should introduce a builder/interface pair in oak to reflect that.
> Users that would like to use such oak-specific extensions would wrap a
> JackrabbitEventFilter and get an OakEventFilter that contains enabling these
> extensions.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
