I reviewed the API docs and the source code and I haven't found a reliable (and efficient) way to determine if the String returned by Messages.getMessage is from the Locale that I requested. It doesn't appear that the returned String will ever be null, but instead will be the message from the default Locale or an error message if that key is not found in the requested or default Locales.
I agree that Messages.getMessage is already heavily overloaded, but IMHO adding methods that accept an array of Locales or modifying the existing methods to accept an array of Locales would be acceptable in the context of a framework that is designed to aid internationalization. duke James Mitchell wrote: > Why not implement the preferred order in your own code? > > ... > ... > myMsg = Messages.getMessage(<German>, <key>); > if (myMsg == null) myMsg = Messages.getMessage(<French>, <key>); > if (myMsg == null) myMsg = Messages.getMessage(<English>, <key>); > ... > ... > > > This way Commons-Resources doesn't have to be convoluted with a bunch of > switches for something very few users are likely to need. > > > > -- > James Mitchell > Software Engineer / Open Source Evangelist > Consulting / Mentoring / Freelance > EdgeTech, Inc. > http://www.edgetechservices.net/ > 678.910.8017 > AIM: jmitchtx > Yahoo: jmitchtx > MSN: [EMAIL PROTECTED] > > > > > ----- Original Message ----- From: "duke" <[EMAIL PROTECTED]> > To: <[email protected]> > Sent: Wednesday, May 11, 2005 5:47 PM > Subject: [Resources] RFE: Support for multiple Locales in > Messages.getMessage > > >> Currently the Messages.getMessage methods only support a single Locale. >> So if you had an application that provided English (default) and French >> resources and a user preferred to read German, French, and English (in >> that order), a call to Messages.getMessage(<German>, <key>) would return >> the message from the English resource when the message from the French >> resource would be preferable. >> >> This RFE calls for the Messages.getMessage methods to accept an array of >> Locales where they currently accept a single Locale. The implementation >> would then search for the specified key in each of the resources for the >> specified Locales in element order. >> >> Using the example above, a call to Messages.getMessage(<German, French, >> English>, <key>) would then return the message from the French resource. >> >> Any other thoughts on solving this problem? >> >> duke >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
