I've been playing around with the export functionality and even after 
implementing the filter, I having issues with it. Originally, we intended 
on having the tag itself handle all of the details about exporting the 
data. Now, we've implemented a solution for Struts Tiles, that uses a 
response filter configured within the web.xml. Is there any reason, we 
shouldn't just abandon the filter approach and implement an export 
servlet? If we already require a change to the web.xml, at least a servlet 
could handle the request properly and we'd avoid all the extra JSP 
newlines and garbage.

Regardless, the export filter isn't working very well for us, so I may 
have to write a servlet. Any thoughts?



-------------------------------------------------------
This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek
For a limited time only, get FREE Ground shipping on all orders of $35
or more. Hurry up and shop folks, this offer expires April 30th!
http://www.thinkgeek.com/freeshipping/?cpg=12297
_______________________________________________
displaytag-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/displaytag-devel

Reply via email to