Why not just do what WW1 had and create a base class for each tag, something
like HTMLComponentTag that has all the HTML attributes in it? (onchange,
onmouseup, class, style, id etc)
As long as the attributes apply to all the elements corresponding to the subclasses. Struts (damn it, I'm trying to quit, I promise :) makes the mistake of having a base class like this too, but the subclasses don't always leverage what the parents can do (i.e. they simply remove the attributes from the TLD, but the class still has the setters).
One place where XDoclet does come in handy, is for TLD generation. It would be impossible to use XDoclet on the Struts tags because they are designed backwards. A child class should embrace everything the parent has to offer, not reject it. Not that you're proposing that, just wanted to impart an issue with similar tags.
Erik
------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01 _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
