--- Arron Bates <[EMAIL PROTECTED]> wrote: > > --- Joe Germuska <[EMAIL PROTECTED]> wrote: > > > > > Whether the "classic" and "el" taglibs are one chunk or two > isn't > > > >> hugely important to me either -- I would prefer that this > decision > > > be > > > >> made by developers who've done more work on that code to date. > > > >> However, I did find that when I patched > > > >> o.a.s.t.html.JavascriptValidator, I had to go and make a > > > >> corresponding change in the EL version. I suspect that changes > in > > > >> those two libraries are going to track pretty tightly. But like > I > > > >> said, I'm not pushing for this; just floating it... > > > > > > > >Is there any reason that the EL tags wouldn't replace the existing > tags > > > >for Struts 2.0? Also, IMO, many of the tags can be removed > entirely > > > for > > > >2.0 because they've been replaced by more powerful counterparts in > the > > > >JSTL. > > > > > > As I've been saying (a lot, it seems, lately) on struts-user, I > think > > > there are legitimate Struts JSP tags like "html:messages" that are > > > not best replaced by JSTL. Any time Struts tools put resources in > > > special locations in request or session scope, I think it's nice to > > > have tags which know the special locations, instead of expecting > > > people to dig in and find them. And, for example with > html:messages, > > > the message-property filtering is a useful feature that would > require > > > a lot of verbose JSTL to achieve the same goal. > > > > > > So, I'd suspect even in 2.0 there will be arguments for a small > > > Struts taglib. But I am 100% on board with pushing people to use > the > > > JSTL where it is really equivalent. > > > > Yep, notice I mentioned removing "many" tags and not *all* tags :-). > > There are certainly tags we should keep around but I just don't see > > a need for most of the logic and bean tags in Struts 2.0. > > > Widely known is that the Struts tags sit under the nested tags. And that > JSTL > and EL cannot fill the shoes of the nested tags. If Struts doesn't want > to > support the taglibs, then thats a separate issue.
Are we really still kidding ourselves that the taglibs are currently supported? No committer actively takes care of them. No one in the community responded to Ted's invitation to support them. We've all moved onto JSTL, JSF, Velocity, XSLT, etc. While the rest of the world migrates to newer/better technologies, we're stuck supporting tags that fewer and fewer people actually use. IMO, it's almost irresponsible to distribute <logic:iterate> with a Struts minimum Servlet level of 2.4 where <c:forEach> is available. David > But for the nested > tags to > do what they do, they need the Struts tags including all the logic tags. > I > don't think that we'd drop all the tags, but as for letting "some" go > that > aren't in JSTL et al... -1 > > > Btw: I've thought long and hard about how to get the nested concept into > JSTL > (to remove the dependancy on Struts), but it's just not a fit. The > nested tags > manage things as much for the trip back to the Struts servlet as much as > making the viewing layout code easier. Nested tags live on Struts. > > > I've watched these conversations, but just don't have the time for all > the > backround study it'd take to make worthy comment. But for the tags, > things > haven't changed. So, apologies for just piping in on familiar topics. I > probably needed a pair of them fantastic gloves already mentioned... > > > Cheers, > > Arron. > > > > > > David > > > > > > > > Joe > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > __________________________________ Do you Yahoo!? Yahoo! Finance Tax Center - File online. File on time. http://taxes.yahoo.com/filing.html --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
