Martin Cooper <[EMAIL PROTECTED]> wrote: > For a very long time now, we have had a strict policy of not including > anything that is not part of the HTML 4.01 spec or XHTML spec. I am > still very much in favour of that policy, and am actively > disinterested in seeing non-conforming additions to Struts.
Donald appears to be asking that the taglib library be made more extensible in general. He is not asking that some specific non-HTML 4.01/XHTML tags be added to struts. Donald, my suggestion is that you post a patch providing such functionality to bugzilla, and it'll either be included or someone will comment on how it needs to be improved. While I myself am vehemently-opposed to vendor-specific html and do everything in my power to keep it (and javascript) out of my apps, I can understand why an internal web app might need such functionality. -Mike > On Tue, 19 Oct 2004 17:13:46 -0400, Kichline, Don (EM, PTL) > <[EMAIL PROTECTED]> wrote: > > I am proposing that the Struts HTML tag library be extended slightly to accept any non-standard attributes. Searching on the new groups, I have been hearing that developers are very strict on supporting a proprietary single-vendor lock-in. What I am proposing is a generic work around for this problem that will not tie struts into any single-vendor specific attributes. > > > > Pass in a Properties class with key/value pairs into the tag. The tag will then iterate through the Properties and output the pairs as attributes into the tag. > > > > We need this at my place of work. We do not want to fork our own version of struts to do this. So we were hoping that a more generic solution might be acceptable to your eyes. > > > > Thank you, > > > > Donald R. Kichline > > Senior Programmer/Analyst --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
