i would be happy to put my name against this (and a matching test case) if no one else has already.
a quick question on the preferred approach: a) quick (and dirty) would be to take a copy of the existing html taglib and hack... b) i'd prefer to look for commonality in the 2 taglibs and just subclass for the separate bits. this may also have advantages for wml or xforms? perhaps the package structure might be: org.apache.struts.taglib.xml org.apache.struts.taglib.xml.html org.apache.struts.taglib.xml.xhtml obviously b) has greater impact on the existing code. perhaps this could be retrofitted once xhtml was up and running? what do you think? tim -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
