My apologies for not understanding this particular issue. There are some liberties that by necessity need to be taken with the tag library definitions, i.e. styleClass for class. I don't understand why someone would care if there are 'excess' tags in the tag library. I would never consider looking at the tag library to determine the availability of a tag and if someone choose to use an attribute that is not supposed to be in the html, html will (is supposed to) ignore it.
My apologies in advance to the original struts designers as I assume they had there reasons for the design choices. But, I have issues with the design of the 'html' equivalent struts tags. They are not constructed the way the html specification is designed. For example in html there is one tag for input with multiple types, in struts there are multiple tags (all of which require tld entries). If the struts tags were constructed in a fashion which matched the html spec, then many of the issues with excess tags would go away. -----Original Message----- From: Martin Cooper [mailto:[EMAIL PROTECTED]] Sent: Tuesday, October 15, 2002 10:43 AM To: 'Struts Developers List' Subject: RE: LabelTag Unfortunately, it's not that simple with the Struts tags. Many of the tags extend a base class which defines a number of common attributes. However, just because the code for an attribute is available does *not* mean that it should be exposed for every tag that extends the base class. A case in point is the HTML taglib. Which attributes are exposed for a particular tag is dependent upon the HTML 4.01 spec. In the implementation, it is very convenient to have several base classes which cover the large majority of attributes. However, there are some tags which extend the base classes, but which do not expose all of the attributes, so that they conform to the spec. Now, if we could get XDoclet to handle that... ;-) -- Martin Cooper -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
