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=18226>.
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=18226

Load Balancing with MessagResources

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|INVALID                     |



------- Additional Comments From [EMAIL PROTECTED]  2003-03-21 15:53 -------
I agree. But this can present problems in some instance, but may not 
necessarily be a bug.

As Struts get used in more and more environments, we run into the bleeding 
edges once in a while. One place that was recently discovered is that some 
application servers insist on application scope beans (i.e. servlet context 
resources) being Serializable under certain circumstances. (Note -- this is not 
a spec requirement issue; it is a container-specific restriction). The Struts 
example application is not going to work in such an environment, because of the 
way that the pseudo-database is architected and used. However, a more serious 
issue is that the MessageResources class (used to store the application 
resources for your internationalized message strings) is not Serializable, and 
it cannt be made so -- because the underlying java.util.ResourceBundle family 
of classes are not Serializable. There is an additional headache that is caused 
by the current implementation -- it relies on loading properties files to 
initialize the message strings. For languages that use ISO-8859-1 character 
sets, that is pretty easy -- just edit the files with a text editor and you are 
done. For other character sets, however, you have to remember to 
run "native2ascii" on the properties files after editing.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to