On 17/10/16 09:38, "Carsten Ziegeler" <cziege...@apache.org> wrote:
>Chetan Mehrotra wrote >> On Mon, Oct 17, 2016 at 11:04 AM, Carsten Ziegeler >><cziege...@apache.org> 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 >property >2. And - as you note - ObserverConfiguration needs a getter method to >expose the hint to the (jcr) implementation I've added a patch with the above to SLING-6164 - would that then be feasible to be included in the API? Cheers, Stefan -- https://issues.apache.org/jira/browse/SLING-6164
