Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
i18n 2.4.4
-
None
Description
After fixing SLING-4910 there is still a very slim chance that the resource resolver is being null while being used within the scheduleReloadBundles, because that is called, before the resolver is initialized. The chance to see that in reality is close to zero though, because scheduleReloadBundles is using the resource resolver only in a scheduled thread.
Attachments
Issue Links
- is broken by
-
SLING-4910 NPE in JCrResourceBundleProvider
- Closed