commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 24941] - LocaleBeanUtils.populate() doesn't accept localized input map
Date Sat, 17 Jan 2004 15:41:28 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24941>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24941

LocaleBeanUtils.populate() doesn't accept localized input map





------- Additional Comments From rdonkin@apache.org  2004-01-17 15:41 -------
hmmm....

> let say we have two users on the server, there is simple thread issues:
> - user A: LocaleBeanUtils.setDefaultLocale(localeA);
> - user B: LocaleBeanUtils.setDefaultLocale(localeB);
> - user A: LocaleBeanUtils.populate(beanA, propertiesA); //converts using localeB

this is really a recommended usage issue rather than simply a thread issue. the design suggested

stutz seems to lead users towards the above senario. (i suspect thta stutz used the beans
rather 
than the static facades and had a separate one for each Locale and so the above scenario could

never happen.)

i suppose a typical usage for this would be where a request arrives at the server which is
associated 
with a user whose locale is A. the population needs to take into account that the user is
in locale A. 
i agree that 

LocaleBeanUtils.populate(Object bean, Map properties, Locale locale)

seems more natural than first setting the default locale.

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message