Actually if it is something that occurs on every request im not even sure I would go the filter route. Post processing the html is going to be expensive in terms of performance then no matter what you do. I would probably reconsider the architecture and see if I couldn't somehow pre-process the html either by the addition of request attributes or something so that the jsp renders what I want instead of doing it in the filter by post processing. If it is just an occasional request then you could probably get away with the filter and doing xslt, or some other parsing without a huge negative impact. Lets face it there will be some impact on at least some requests no matter what :)
Al -----Original Message----- From: Frank W. Zammetti [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 06, 2005 10:06 AM To: Struts Users Mailing List Cc: user@struts.apache.org Subject: Re: [OT] edit HTML code on fly using java If your HTML is valid XHTML, you should be able to apply XSLT transformations on it without too much trouble. But, this would be an expensive operation per request, probably a VERY expensive one at that, so if it is something that is going to happen frequently I wouldn't go this route. In fact, if it is anything other than trivial changes and it will be frequent (on every single request?), my first instinct would actually be to use string manipulations because I think you would be hard-pressed to find something else that performs well enough (assuming your code was relatively tight of course). I'm sure something is out there, but if we're talking something that happens every request, I'd certainly want maximum control over it. -- Frank W. Zammetti Founder and Chief Software Architect Omnytex Technologies http://www.omnytex.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
