[
https://issues.apache.org/jira/browse/SLING-3147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Klimetschek resolved SLING-3147.
------------------------------------------
Resolution: Fixed
Fix Version/s: i18n 2.2.8
Thanks!
It seems some of the automagic refreshing added in OAK-803 solved the problem
on our application stack already, so I couldn't reproduce this anymore. But
that magic is only intended for a few oak releases to ease application
migration, so the explicit refresh() is still the right thing and based on your
integration tests I am quite sure this was the cause of the issue. The updated
sling.i18n bundle works fine. I created an internal release of it.
So I am resolving this as fixed.
> Oak: i18n dictionaries observation no longer works
> --------------------------------------------------
>
> Key: SLING-3147
> URL: https://issues.apache.org/jira/browse/SLING-3147
> Project: Sling
> Issue Type: Bug
> Components: Extensions, Oak
> Affects Versions: i18n 2.2.6
> Reporter: Alexander Klimetschek
> Labels: i18n
> Fix For: i18n 2.2.8
>
>
> When running Sling with Oak, the JcrResourceBundleProvider [0] in the i18n
> bundle apparently no longer gets the observation events for sling:message
> nodes in the JCR. This means that changing a string in the repo or installing
> a package with new translations won't have an effect if the resource bundle
> is already loaded in memory.
> Workaround is to restart the i18n bundle after every string change.
> [0]
> http://svn.apache.org/repos/asf/sling/trunk/contrib/extensions/i18n/src/main/java/org/apache/sling/i18n/impl/JcrResourceBundleProvider.java
--
This message was sent by Atlassian JIRA
(v6.1#6144)
