Error message severity not translated correct when locale is changed

Question

We have a shell page displaying different task flows within a dynamic region. The shell page f:view tag has locale="#{LocaleManager.currentLocale}" to allow programmatic change of locale. Most of the flows uses the locale from the browser request (e.g. Danish) but some pages has fixed locale (en_US) and will always be rendered with this locale (don't ask me why. It's a requirement). For those fixed locale pages, the expression #{LocaleManager.currentLocale} always returns "en_US". It works nice, but we have a strange problem with the translation of error messages displayed by validators/converters. E.g. if a character is entered in a number field, the user will see the usual popup error message like "*Error:* The value is not a number". The message part of the error message is translated but the severity message prefix ("Error:" in the example), seems to be translated and cached once per session. If the error message popup has been displayed once in a different locale, then after change of locale, the severity message prefix continues to use the translation from the first display. The message part of the message is translated perfectly.
Let me give an example:
1) User enters da_DK page and enters a invalid number. Error message displayed: "*Fejl:* Værdien er ikke et tal"
2) User enters en_US page and enters a invalid number. Error message displayed: "*Fejl:* The value is not a number"
If the examples is reversed, then the error messages will be:
2) "*Error:* The value is not a number"
1) "*Error:* Værdien er ikke et tal"
Do anyone know how to clear this translated severity message prefix, when locale is changed? Or is there a better way to overcome this issue?
We're using JDeveloper and ADF 11.1.2.2 and are able to reproduce the issue on the embedded weblogic.

Answer 1

Hi again
ok I added another locale that ships with flash builder, and encoutered the same problem
whenever I change the locale, the error tooltips are gone
I was even able to fix both new locales by assigning the the validators custom error messages using resourceManager.getString() like i assign a value to all other UI strings in the application
the default locale which is specified in the project compiler's parameters is en_US
and my final question to you is:
is there a best practice regarding localizing & managing the error massages Flex SDK uses?
what is the internal path to the resource bundles that flex uses to display errors?
it seems like it makes more sense to copy and edit an existing list of errors, rather then blow up the application code...
can you please share your view on the matter
thank you for your help
Yariv