Henri Yandell wrote:
The Taglibs project has been dead for years. I'm sure it's not going to improve; taglibs are a pain to implement (especially if support is targeting older JSP specs), JSTL replaced many and at the same time JSP stopped being the obvious choice for web applications. It's frustrating to both users and committers to have the project sitting with doors apparently open, so I'd like to suggest a closing up of shop.
Using a similar argument - app servers are a pain to implement and Java stopped being the obvious choice for web applications - one could argue that Tomcat should pack it in. Obviously, I disagree that those are valid reasons for taking action. I'm also at a loss as to what having the "doors apparently open" implies. I can't recall many (any?) user questions posted to the list going unanswered. A few of the answers might amount to, "Yup, looks like a bug, but that taglib isn't currently under development", but they're still answers ;-).
For me, the biggest difference between Taglibs and a project like Tomcat is simply the community. That's the focus of Apache, right? So, the only justifiable reason for "closing up shop" would be the loss of community (dev and/or user). Unfortunately, that's a difficult argument to refute for Taglibs and I agree that the situation is unlikely to improve. My guess is that Tomcat and Geronimo are probably serving the community needs of the users.
I'm not sure I understand exactly what you're suggesting from a big-picture perspective. Do you think that the entire Taglibs project should go away or do you think that it should remain but only support three taglibs: Standard 1.1, Unstandard and RDC?
Here's what I'm thinking: 1) Standard Taglib 1.1.3 release. This is getting pretty close, so it would be very nice to get a release out.
Sure. I'm happy to do some more work on it.
2) RDC Taglib needs to continue. It's not had a lot of activity recently, but I'm presuming that Rahul is still active on this one and that it would need to continue. My suggestion is that it joins Jakarta Commons (either at jakarta.apache.org/commons or commons.apache.org if Commons moves there). Its build system could be brought up to date too.
Can't really speak to that, but Rahul's already responded. I couldn't locate it, but I thought there was supposed to be some sort of generic "Web Components" project. Ring a bell for anyone else?
3) Others would be end of lifed - with a request going out to find out which ones are strongly active. I would still like to coalesce many into the sandbox'd Unstandard Taglib, ie) a single taglib with various bits of value that JSTL did not replace (and making it JSP 2.0 or 2.1 specific); so I am interested in hearing which functionalities are valuable.
Kicking a useful Unstandard release out the door would be great. I'd be happy to work on that as well. Since Standard 1.1 is a JSP 2.0 taglib, it seems like it would make sense to target that as well.
Target date for all of this would be the end of this year. Hen
-- Kris Schneider <mailto:[EMAIL PROTECTED]> D.O.Tech <http://www.dotech.com/> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
