On Wed, 23 Jun 2004 13:52:23 -0700 (PDT), David Graham wrote: > IMO, Struts 2.0 is a good time to leave the old tags (defined as > ones with JSTL replacements) behind. Struts 1.x apps would still > have them available but 2.x apps would use the JSTL. I consider it > a disservice to the communtity to distribute Struts specific > versions of the more powerful and standardized JSTL tags. > > Note that none of my comments are directed at Struts tags that > actually add value to the framework and don't have standardized > replacements. > > David
There's an old saying among Apaches: "Let Darwin decide." If the JSTL is both powerful and standardized then the other tags will naturally fall into disuse. The stronger will survive. It's important to note that some of the "power" of the JSTL derives from experience with scripting languages like Velocity. People have often said the same kind of things about Custom Tags versus Velocity as is now being said about Struts tags versus the JSTL. But, if the Velocity developers had followed that advice, the JSTL would not be as powerful as it is today. We pulled back on tag development for a very long time for the sake of the JSTL. But, we have long since reached the point where the JSTL has to swim or sink on its own. It is certainly our job to ensure the appropriate specifications are observed when they apply. But it is not our job to prefer one specification over another. Custom Tags are a specification too. If the community supports the Struts custom tags, then it's our job to help or get out of the way. 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. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
