Menu

#1055 Localisation-fallback doesn't work (null instead of default value)

1.2
open-postponed
5
2010-07-03
2010-07-03
jfirechief
No

DO NOT EDIT OR ANSWER THIS ISSUE. SEE THE ORIGINAL ISSUE INSTEAD:
https://www.jfire.org/modules/bugs/view.php?id=1428
ORIGINAL REPORTER: marco

When using a default messages.properties in combination with an incomplete language-specific file (e.g. messages_en.properties), the fallback-mechanism doesn't work properly:

In the invoice, the letter's subject is rendered via JavaScript and should result in sth. like "Invoice 2009/123". However, with "Invoice" being in the messages.properties (and missing in the messages_en.properties), the output is "null2009/123".

Here's the JavaScript:
***
articleContainerType = "";
articleContainer = JFireReportingHelper.getVar("articleContainer");
className = articleContainer.getClass().getSimpleName();
articleContainerType = reportContext.getMessage("articleContainer.name."+className, reportContext.getLocale());
articleContainerType + " " + articleContainer.getArticleContainerIDPrefix() + "/" + articleContainer.getArticleContainerIDAsString()
***

Thus, the error is somehow in the reportContext.getMessage(...).

Discussion

  • jfirechief

    jfirechief - 2010-07-03

    ORIGINAL COMMENT BY marco, VIEW IT HERE:
    https://www.jfire.org/modules/bugs/view.php?id=1428

    The variable "reportContext" comes from BIRT - not JFire. Thus, the method getMessage(...) [which btw. exists without the locale argument, too] needs to be fixed in BIRT and we should postpone further work on this after we updated to the new BIRT.

     
  • jfirechief

    jfirechief - 2010-07-03
    • labels: --> JFireReporting
    • milestone: --> 1.2
    • assigned_to: nobody --> ichigokun
    • summary: Localisation-fallback doesn't work (null instead of default value) --> Localisation-fallback doesn't work (null instead of default value)
    • status: open --> open-postponed
     

Log in to post a comment.

MongoDB Logo MongoDB