Use them together where it makes sense. Struts integrates your properties within sub-applications, and will switch to the appropriate bundle for you. This is one place you may well be better off using Struts itself. Note that, with the contribution of the struts-el taglib by David M. Karr (should be available in nightly builds - the contrib area - soon), you can have the "best of both worlds". Struts tags for interoperating with Struts, and the JSTL EL within them. This is a powerful, handy feature. There are, of course, areas which you can completely replace Struts' taglibs with their JSTL counterparts, and it's advised that you do so. The JSTL is "the standard", after all.
Vernon Wu wrote: >That can't be true since JSTL comes after the Struts tag library. > >What is your definition of "easier"? > >9/23/2002 4:22:21 PM, Matt Raible <[EMAIL PROTECTED]> wrote: > >>It seems that Struts makes it much easier to do i18n than JSTL. Please >>correct me if I'm wrong. >> >>Struts = <bean:message key="index.title"/> >> >>JSTL = >> <fmt:bundle basename="org.roller.presentation.AppResources"> >> <fmt:message key="index.title"/> >> </fmt:bundle> >> >>Thanks, >> >>Matt >> -- Eddie Bush -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
