struts-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ted Husted <>
Subject Re: Short term plans
Date Sat, 01 Mar 2003 12:31:10 GMT
First, David was probably trying to be helpful. (Why reinvent the wheel?)

But to answer your question, I think the litmus test would be whether 
there is a working patch annexed.

All anyone has said is that since the attention of the Committers in 
their own work is likely to be on other technologies, it is equally 
likely that the Committers won't be spending their *own* development 
time *creating* patches.

As long as the change has technical merit, and a Committer is willing to 
take responsbility for the patch, we won't/can't veto something becomes 
of competition from JSTL/JSF/XLST/Velocity/Tapestry/lord-knows.

Meanwhile, if we have a good suite of tests, and a patch comes along, it 
will be easier for any of us to commit it (since the tests will help 
catch any problems).


John Yu wrote:
> With respect (too :-), what criteria should/would the (developer) 
> community use to strike a balance, both ensuring the quality and 
> relevance of Struts taglibs (JSP 1.1 dependent) and migrating users 
> gradually to JSTL (JSP 1.2 dependent)?
> For instance, in a recent feature request:
> As David, the recently crowned MVC (what an acronym), pointed out the 
> requested feature for <bean:message> is already available in JSTL 
> <fmt:message>. Is there an easy litmus test for Struts users to 
> guestimate if an enhancement is worthwhile requesting?
> regards,

Ted Husted,
Struts in Action <>

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message