T
Tony Piazza
My project team is considering whether to switch from the Struts
<bean:message> tag to the JSTL <fmt:message> tag for displaying localized
text in our application. Our existing code provides a resource factory that
is specifed in the struts-config.xml file. I have been researching how to
use the JSTL internationalization support and I have a few questions for
those of you who have already been down this road:
(1) It is not clear to me exactly what I am supposed to provide for the
LocalizationContext <context-param> tag in the web.xml file. Is there a way
to take advantage of our existing resource factory?
(2) Besides replacing the <bean:message> tags with <fmt:message> tags, are
there any other changes to the application that are necessary?
(3) I have read some rumblings about the JSTL's internationalization support
being inferior to that of Struts. Is this true and if so, what are the
specific shortcomings of JSTL's approach?
Thanks in advance for any assistance you can provide!
Tony Piazza
<bean:message> tag to the JSTL <fmt:message> tag for displaying localized
text in our application. Our existing code provides a resource factory that
is specifed in the struts-config.xml file. I have been researching how to
use the JSTL internationalization support and I have a few questions for
those of you who have already been down this road:
(1) It is not clear to me exactly what I am supposed to provide for the
LocalizationContext <context-param> tag in the web.xml file. Is there a way
to take advantage of our existing resource factory?
(2) Besides replacing the <bean:message> tags with <fmt:message> tags, are
there any other changes to the application that are necessary?
(3) I have read some rumblings about the JSTL's internationalization support
being inferior to that of Struts. Is this true and if so, what are the
specific shortcomings of JSTL's approach?
Thanks in advance for any assistance you can provide!
Tony Piazza