Bertrand Delacretaz wrote
> Hi Carsten,
>
> On Tue, Feb 2, 2016 at 4:24 PM, Carsten Ziegeler wrote:
>> ...With the new observation api we have a more
>> elegant solution: you can register the listener with a relative path and
>> the search paths are automatically added
Hi Carsten,
On Tue, Feb 2, 2016 at 4:24 PM, Carsten Ziegeler wrote:
> ...With the new observation api we have a more
> elegant solution: you can register the listener with a relative path and
> the search paths are automatically added
Do we have docs or examples that
Hi,
I was looking at a few cases where we use an administrative
ResourceResolver just to get the current search paths, for example in
ScriptCacheImpl [1], the (simplified) pattern is:
ResourceResolver resolver = rrf.getAdministrativeResourceResolver(null);
searchPaths =
This pattern is usually used with registering event handlers as
observation listeners. With the new observation api we have a more
elegant solution: you can register the listener with a relative path and
the search paths are automatically added.
As all our event handlers should move to the new