Re: ResourceResolverFactory restart behaviour

2015-09-15 Thread Konrad Windszus
Yes, SLING-4360 added a check if the RRF is live to the method ResourceResolver.isLive(). The problem is that you have to call that method explicitly. For me the use case is rather to detect programming mistakes like not listening for ResourceResolverFactory restarts. What about implicitly

Re: ResourceResolverFactory restart behaviour

2015-09-15 Thread Konrad Windszus
Ok, thanks for the confirmation. I created issue https://issues.apache.org/jira/browse/SLING-5025 for that. The only question is, whether the check for context.isLive() should also be done within the checkClosed()? In theory I guess one could still use a resource resolver if one of the used

Re: ResourceResolverFactory restart behaviour

2015-09-15 Thread Carsten Ziegeler
Am 15.09.15 um 08:37 schrieb Konrad Windszus: > Yes, SLING-4360 added a check if the RRF is live to the method > ResourceResolver.isLive(). The problem is that you have to call that method > explicitly. > For me the use case is rather to detect programming mistakes like not > listening for

Re: ResourceResolverFactory restart behaviour

2015-09-15 Thread Carsten Ziegeler
Am 15.09.15 um 09:50 schrieb Konrad Windszus: > Ok, thanks for the confirmation. I created issue > https://issues.apache.org/jira/browse/SLING-5025 for that. > The only question is, whether the check for context.isLive() should also be > done within the checkClosed()? > Yes, I think checkClosed

ResourceResolverFactory restart behaviour

2015-09-14 Thread Konrad Windszus
Currently if the resource resolver factory is restarted (e.g. because the configuration has been changed) all resource resolvers which were being requested beforehand become almost useless, because they have no longer any providers being bound! This means those resolvers can only be used to

Re: ResourceResolverFactory restart behaviour

2015-09-14 Thread Carsten Ziegeler
Am 14.09.15 um 17:51 schrieb Konrad Windszus: > Currently if the resource resolver factory is restarted (e.g. because the > configuration has been changed) all resource resolvers which were being > requested beforehand become almost useless, because they have no longer any > providers being

Re: ResourceResolverFactory restart behaviour

2015-09-14 Thread Konrad Windszus
Thanks Carsten, indeed I am hitting SLING-4974. Could you point me to the commit which closes the resource resolvers after the restart of the factory (or after some required providers become unavailable)? I couldn’t find any related commit in

Re: ResourceResolverFactory restart behaviour

2015-09-14 Thread Carsten Ziegeler
Am 14.09.15 um 18:04 schrieb Konrad Windszus: > Thanks Carsten, indeed I am hitting SLING-4974. > Could you point me to the commit which closes the resource resolvers after > the restart of the factory (or after some required providers become > unavailable)? > I couldn’t find any related commit