Mark, the methods they delegate to encapsulate the same logic and even more because of the extra argument they take in that specifies whether other locales should be searched.
Wyclif On Tue, Sep 20, 2011 at 5:43 PM, Mark Goodrich <[email protected]> wrote: > Looks like there was a change in the methods on Concept for fetching a > Concept Name for a Locale between 1.6 and 1.8. > > In 1.6 the following two methods existed: > > getBestShortName(Locale) > getBestName(Locale) > > These methods had fairly intelligent logic for fetching a name based on > locale... specifically, they would check separately for matches between the > language and country components of a locale. For instance, if you had a name > "Some Name" for the locale "en", and you did a getBestShortName(new > Locale("en_GB")), the methods were smart enough to return the "Some Name" as > the name if no name for the exact locale en_GB was found. > > In 1.8 these methods have been depreciated, and now delegate to methods > that only match on exact locales (getBestShortName(new Locale("en_GB") would > return null in the previous example). > > Was there a reason for this? It looks like there are methods > getShortNameInLanguage and getShortNameForCountry that I can use to > approximate the previous functionality, but these methods have been > depreciated as well. Am I missing something? > > Thanks, > Mark > > _________________________________________ > > To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to > [email protected] with "SIGNOFF openmrs-devel-l" in the body > (not the subject) of your e-mail. > > [mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l] > _________________________________________ To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to [email protected] with "SIGNOFF openmrs-devel-l" in the body (not the subject) of your e-mail. [mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l]
