Expand my Community achievements bar.

SOLVED

Resource Bundles in source missing

Avatar

Level 3

I can't seem to locate any resource bundle properties files in the source...isn't this available also?  I need to change some labeling, specifically:

    _label.text = Localization.impl.getString(ROLE_STRINGS[_data.role]);

thanks,

David

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

Hi there,

In order to be Flex-independent, we had to build a Localization Framework

that didn't depend on resource bundles. That said, you should be able to

plug resource bundles in pretty easily.

Localization.impl = new MyLocalizationManager();

Then, make a MyLocalizationManager class which implements

ILocalizationManager - the method you specifically need to implement is

getString(). You can pull the string from your resource bundles in that

method.

nigel

View solution in original post

3 Replies

Avatar

Employee

Hi David,

We just have a place holder for Localization for LCCS, so the code snippet you sent does nothing. So you can hard code the string you want.

Thanks

Arun

Avatar

Correct answer by
Former Community Member

Hi there,

In order to be Flex-independent, we had to build a Localization Framework

that didn't depend on resource bundles. That said, you should be able to

plug resource bundles in pretty easily.

Localization.impl = new MyLocalizationManager();

Then, make a MyLocalizationManager class which implements

ILocalizationManager - the method you specifically need to implement is

getString(). You can pull the string from your resource bundles in that

method.

nigel

Avatar

Level 3

Thanks, I see how this is working...made the assumption this was using standard resource bundles...thanks!

The following has evaluated to null or missing: ==> liqladmin("SELECT id, value FROM metrics WHERE id = 'net_accepted_solutions' and user.id = '${acceptedAnswer.author.id}'").data.items [in template "analytics-container" at line 83, column 41] ---- Tip: It's the step after the last dot that caused this error, not those before it. ---- Tip: If the failing expression is known to be legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)?? ---- ---- FTL stack trace ("~" means nesting-related): - Failed at: #assign answerAuthorNetSolutions = li... [in template "analytics-container" at line 83, column 5] ----