Details
-
Improvement
-
Status: Closed
-
High
-
Resolution: Fixed
-
3.2.3
-
None
-
None
-
1
-
Platform Sprint 148
Description
When resource bundles are changed, currently all resource bundles are unregistered, and not only the resource bundles that were changed. Therefore all resource bundles have to be reloaded into the HST.
When all resource bundles are unregistered at once. This can have an impact on the performance. Especially in a situation where there are lots of resource bundles, that are accessed very frequently, this can have the side effect that lots of resource bundles are loaded at once.
Attachments
Issue Links
- causes
-
HSTTWO-3952 Resource bundle registry not invalidated on replication / JCR change
- Closed
- is backported by
-
HSTTWO-3903 [Backport to 4.1] Fine grained resource bundle reloading (instead of unregistering all at once)
- Closed
-
HSTTWO-3904 [Backport to 4.0] Fine grained resource bundle reloading (instead of unregistering all at once)
- Closed
-
HSTTWO-3905 [Backport to 3.2] Fine grained resource bundle reloading (instead of unregistering all at once)
- Closed
- relates to
-
HSTTWO-3907 Remove deprecated ResourceBundle API in HST 5.0
- Closed