My original point really was that if the standard for Struts continues to be
2.2/1.1 that we should be careful not to reply to the "How do I do this with
<html:???>" questions with the stock answer of "use JSTL".

If we're supporting Struts tags then I believe we should first answer the
question that was asked and *then* offer the advice that JSTL offers an
alternative *if* their environment supports it.

I feel it's become a bit too easy to give the JSTL answer and not deal with
the issue as presented. And I do feel that if there are gaps in the
functionality provided by the current supported environment we should at
least consider additions, particularly if someone has gone to the trouble of
providing a patch.

If someone doesn't want to deal with Struts taglib issues than that's fine,
but if there's no one left who's prepared to provide support then at that
point (and I'm not suggesting that we're anywhere near yet) I would urge
that we reconsider the required platform.

Please read this as a gentle reminder/prompt for discussion, rather than a
stern lecture. It's not my intention to cause any offence and it's something
I need to be aware of as much as anyone.

                O
           _   /|\
soapbox-> |x|  / \  <- me, no longer on it :-)

Steve


> -----Original Message-----
> From: Ted Husted [mailto:[EMAIL PROTECTED]
> Sent: August 29, 2003 1:44 PM
> To: Struts Developers List
> Subject: Re: Support for non-JSTL tags (was RE: DO NOT REPLY [Bug 21465]
> - Enhancement of the html:link tag)
>
>
> Craig R. McClanahan wrote:
> > I'm -1 on making Struts 1.2.x dependent on Servlet 2.3 / JSP 1.2.
>
> Ditto. Contrary to popular brief, a great number of organizations have
> *not* migrated to 2.3/1.2, including some of the largest companies in
> the world.
>
> -Ted.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to