Hi Jörg
I would argue that a new ResourceResolver for each "onEvent" call
would be advisable. Not only to avoid the problem you observe, but
also to avoid the risk of the session being used concurrently from
multiple threads. Not sure if JCR event hanlders may be called
concurrently though.
The a
Hi all,
I just came across an exception which makes me wonder how to adress it;
it's a JCR observation listener, which has been opened on the JCR session
of a Sling ResourceResolver. And inside of the event handler the
isResourceType() method of the Resource Resolver is called.
27.08.2018 11:16:4
