> Oh well, I guess I'll look elsewhere for a framework. If you can only use a framework that only bundles everything into one monothlitic distribution, then yes you should. We tried that, and it is clearly not working. If monolithic is the only way we could do things in the future, then I would go emeritus myself.
If you would prefer a granular framework that lets you install only the components that you use, then stick around. Since the current committers are obviously too busy to work on Struts, we're going to need more people willing to do what needs to be done. But we can only use people who are willing to be team players and seek win-win paths that work for everyone. The only thing a my-way or the highway attitude is going to get someone is a street map. As far as things like taglibs go, personally, I think we should support the community in doing what the community wants to do, so long as the solution is secure, specification-compliant, and vendor-neutral. Once we are more granular, we could even consider things like a Struts taglib that relied on JavaScript, if there were people to develop and support it. We can't do that now, since there is only one distribution, and we don't want to compel people to rely on JavaScript. But as a separate Struts subproject, it is something what we could consider. -Ted. On Thu, 24 Jun 2004 08:15:35 -0400, Edgar P Dollin wrote: >> Personally, I don't plan to write a set of custom tags for Struts >> 2.0. I would expect Struts 2.0 to be written in such a way that >> custom tags (or Velocity tools) are not needed. But if they were >> needed, and someone wrote a set that was popular within our >> community, then I would consider it a valid prospect for a >> subproject. Though, if we do 2.0 right, I really don't see that >> happening. >> >> -Ted. >> > > Oh well, I guess I'll look elsewhere for a framework. > > > Edgar --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
