Chetan Mehrotra wrote
> On Mon, Oct 17, 2016 at 11:04 AM, Carsten Ziegeler <> 
> wrote:
>>>> I would rather go with a "property names filter hint" - and if we detect
>>> other use cases we add another property for that.
>>> Makes sense. This would keep things simple and precise
>> I plan to release API early this week :) So it would be great if we
>> could get this in, or we move it to the next api release.
> Would ObserverConfiguration be the place to expose this hint part?
This needs enhancements in several areas:
1. ResourceChangeListener we need to define a new service registration
2. And - as you note - ObserverConfiguration needs a getter method to
expose the hint to the (jcr) implementation



Carsten Ziegeler
Adobe Research Switzerland

Reply via email to