You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Alexander Klimetschek (JIRA)" <ji...@apache.org> on 2008/11/04 10:42:44 UTC
[jira] Commented: (SLING-717) I18n: messages with no sling:key
property stop enumeration of all keys
[ https://issues.apache.org/jira/browse/SLING-717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12644930#action_12644930 ]
Alexander Klimetschek commented on SLING-717:
---------------------------------------------
You are right, using the node name as fallback was actually a design goal in some earlier discussion. So I would prefer the second patch as well.
> I18n: messages with no sling:key property stop enumeration of all keys
> ----------------------------------------------------------------------
>
> Key: SLING-717
> URL: https://issues.apache.org/jira/browse/SLING-717
> Project: Sling
> Issue Type: Bug
> Components: Extensions
> Reporter: Alexander Klimetschek
> Attachments: SLING-717.fmeschbe.patch, SLING-717.patch
>
>
> If a sling:message node has no sling:key property, this will stop the ResourceBundleEnumeration, because the null key is added to the resources list in JcrResourceBundle.loadFully() and a null key is also interpreted as the "end marker" in ResourceBundleEnumeration.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.