That's right. It's important to realize that most non-trivial applications will often use more than one tag library. There is no good reason to try to restrict yourself to a single tag library.
In the case of Struts, it's very beneficial to use the Struts tag library along with the JSTL. In addition, the "Struts-EL" contrib package (in the "contrib" directory) is a port of the Struts tags (the ones that aren't directly served by the JSTL), using the expression evaluation engine of the Jakarta Taglibs JSTL implementation. -----Original Message----- From: Tarek M. Nabil [mailto:[EMAIL PROTECTED] You mean there are no equivalents for the Struts HTML tags in the JSTL? -----Original Message----- From: Manish Singla [mailto:[EMAIL PROTECTED] You may replace most of Logic tags/Bean tags with JSTL. You may still want to use HTML tags of struts Your decision may get affected in few cases if you are thinking of migrating to JSF in future Tarek M. Nabil wrote: > Hi everyone, > > I'm getting ready to move from Struts 1.0.2 to Struts 1.1. Since, > also, I now guarantee a J2EE 1.3 container, I'm considering replacing > Struts tag libraries with the JSTL. Before I make this move, I wanted > to know whether, from your experiences, the JSTL gives the same > capabilities as the tag libraries provided with Struts, especially > that I know that the tag libs shipped with Struts 1.1 fix a lot of the > shortcomings of the tag libs shipped with 1.0.2. So, is going with the > standards worth the move? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
