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=10322>. 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=10322 Problems with LookupDispatchAction and other locals ------- Additional Comments From [EMAIL PROTECTED] 2002-07-03 02:13 ------- Ok, the problem is that the resources.getMessage() call wasn't using the locale from the current request. So, it only ever worked for the defaultLocale of the JVM. However, in addition to fixing that there needs to be a lookup map for each language. At least that is how I implemented it. I've patched the nightly build version, and I skipped using synchronized calls intentionally. I have a synchronized patch as well if that is desired. However, even if more than one request goes through the logic, it shouldn't hurt, and it should be less expensive in the short term. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
