On 5/16/07, Henri Yandell <[EMAIL PROTECTED]> wrote:
Based on the Taglibs future email a while back, it sounds like we might have some number of people interested in working on things. Here's a proposal for a general direction: 1) Taglibs contains three active items: * Standard 1.1 (1.0 being considered an older, unsupported release). * Unstandard - containing a merger of all useful parts of the other Taglibs. * RDC. 3) Merge the following into Unstandard. Then retire them. * Log. Tempted to dump commons-logging from trunk and have two log taglibs, one for log4j and one for jdk logging. * DateTime. JSTL replaces this, but before we retire it we should investigate for snippets for Unstandard. * i18n. Same as DateTime. * JNDI. Be interesting to see if there's anything we could grab from this. * Random. Maybe something for Unstandard. Overlap with String.
I can't say I've ever understood what this is useful for. Personally, I'd be for adding it to the 'retire' list. * Regexp. We should investigate whether any of its bits are worth
rewriting on top of JDK 1.4 for Unstandard. * String. Hesistant to push too much of what's in here into Unstandard, but a few might be worth it.
Much of this stuff would be a more natural fit into the JSTL world if it was in the form of EL functions. Not sure if anyone would actually be up for the work to convert them, though. 2) Retire the following:
* DataGrid. Better to work well with and recommend DisplayTag. * Benchmark. Not a big enough deal. * BSF. I wonder if we should offer this over to the BSF project? * Cache. This was never released and should still be in the sandbox. * Input. I don't think anyone is using this anymore. * IO. This stuff should be done in Java imo. * JMS. Messenger was never released. Again, this should be in Java. * Mailer. This is a tough one, users bring it up, and find problems. I'd rather see people being encouraged to work with commons-email with a templating language and dropping this.
Funny you should mention that. When I worked on Mailer (several years and two companies ago), it was because we were using JSP as the template language you mention. ;-) Ultimately that wasn't a great idea, though. * Scrape. Best done in Java methinks.
* XTags. Not used enough. * Ultradev. I'm sure this is ages out of date. * Image. Better as an API, which I think Abey had somewhere. * Mailer2. I'm still not sure about email from jsp pages :) Again, commons-email.
Yeah. Also all the Deprecated's should be Retired.
Thoughts?
I like the idea of lumping the various pieces we want to keep into a single jar, a la JSTL. One thing, though: Wouldn't we want to ensure that all of the pieces in that jar are EL-enabled? Have some enabled and some not would be funky, to say the least. (But then we could be in good shape here and I just don't know it.) -- Martin Cooper Hen
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
