Since that time, the need for Struts to provide basic tag functionality has withered away. The Jakarta Taglibs project thrives, JSTL has long since shipped, and JSF is late early release (to coin an oxymoron). Struts doesn't have to showcase taglibs as a proof of concept anymore.
Personally, I favor the idea that the original html taglib, and friends, should be continue to be maintain and improved. A lot of people just don't have access to the JSTL yet. But, we don't want to be in the datasource business anymore, and we don't want to be in the *generic* taglib business anymore either. There are other places where such things can be done better than we can do them here.
Some good examples of people doing this already are Struts Layout <http://struts.application-servers.com/>
and Struts Menu
<http://sourceforge.net/projects/struts-menu/>.
If someone is not up to starting their own project, I'm sure the Struts SourceForge crew would also be open to Struts-related taglibs being hosted there.
What baffles us is the feeling that absolutely everything has to be part of the core framework. If people have tag implementations they want to share, there are many places where this can be done.
-Ted.
Edgar P Dollin wrote:
For the first time in many months, there was some visible progress in the area of acceptance of submissions on tags. Thank you David and Robert.
I do have some points that I am sure will draw fire, but I have been an idiot on this forum for so long...
1) It is fine that the basic tags in struts don't emit non-standard html, but why do struts tags have to 'police' the emission of non-html. For many intranet style projects, non standard html is important to achieve specific required functionality. To deny the need for such code seems strange.
2) It baffles my mind why struts insists the tags be so minimalistic and non-creative. I am aware of the difficulties in writing tags with the weird life span and semi random instantiation patterns and the bugs that are almost endemic with custom tags. But simple tags like java-script assisted date entry are so basic that simple implementations should be part of struts. Many of us have implementations of this (i.e. Matt Kruse's date functions) but there would be no hope of a submission passing muster.
3) Lastly, there are certain class of business information that the view needs, i.e. readonly, size. The tags should have to ability to easily pass this information from the business tier to the view. Again, the hope of a submission relating to this type of extension being accepted seems iffy, especially since generalizing a specific implementation is a bit of effort.
Edgar
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
