You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Oliver Lietz (JIRA)" <ji...@apache.org> on 2017/03/01 08:59:45 UTC

[jira] [Resolved] (SLING-6511) SlingTemplateResource unable to handle missing localization for a language

     [ https://issues.apache.org/jira/browse/SLING-6511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Oliver Lietz resolved SLING-6511.
---------------------------------
    Resolution: Cannot Reproduce

> SlingTemplateResource unable to handle missing localization for a language
> --------------------------------------------------------------------------
>
>                 Key: SLING-6511
>                 URL: https://issues.apache.org/jira/browse/SLING-6511
>             Project: Sling
>          Issue Type: Bug
>          Components: Engine
>    Affects Versions: Scripting Thymeleaf 1.0.0
>            Reporter: Sajid Momin
>            Assignee: Oliver Lietz
>         Attachments: error.log, javassist-3.20.0-GA.jar, org.apache.sling.scripting.thymeleaf-1.0.0.jar, Test.zip, thymeleaf-i18n-error.log
>
>
> I am currently deploying Sling Thymeleaf HTML template processor to AEM 6.2.  In my attempt to use i18n in my template, I am receiving a null pointer exception.  When the message resolver is looping through the localization of the language, it's unable to skip the processing of the missing localization file resulting in a null pointer.  The only way to fix the issue is to define all localization resource bundle for the language in order to process the template.  It would be nice for the message resolver to ignore the missing localized language resource bundle and continue to the next.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)