Okay, apparently I can't read. It was a <bean:message> tag, not a <bean:write> tag! Since <bean:message> WAS ported to Struts-EL, I assume that there is something you can do with <bean:message> that you cannot do with <fmt:message>. What would that be?
The biggest difference is that <bean:message> is hooked into the internals of Struts. I'm guessing this is most evident when switching modules. However, I've hacked a quick JSTLSwitchAction that seems to keep the default JSTL localization context in sync with module changes.
I'm trying to use as many JSTL tags as possible, and I generally use the Struts-EL README.txt file to tell me what I should use. In this case, the README.txt file would have led me to use the Struts-EL tag when there is an equivalent JSTL tag.
I'm not entirely conviced that I even _need_ to put labels in a .properties file. Is i18n the only reason to do so? I'm 99.9% sure this webapp will *never* need to be displayed in other than English.
One other reason would be the added level of indirection. In other words, it keeps string literals out of your code/page. Even for a single language, you may want to change the actual text represented by a key. If that text needs to appear in more than one place, it's a lot easier to just modify the property file.
-- Kris Schneider <mailto:[EMAIL PROTECTED]> D.O.Tech <http://www.dotech.com/>
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
