Hi Benjamin the filter is needed when the response could be already committed before displaytag is called. When displaytag export data, it should be able to resect the response and change the content type. If "something" has already done that before the export will end up with a "could not reset response" or "response has already been committed" error. This situation tipically occours when using tiles (afaik response is committed after each tile is executed) or also after other custom tags which force the responce to commit (or after any response.flushBuffer(), as you can see on unit tests).
any update to the documentation is welcome, you can edit the "install" document or maybe add it to the faq. fabrizio > > > MY QUESTION: > > > My question is this: what specific problem are we solving > > > here? Could this be the same problem that was mentioned > > > today by Joshi from GS.com? I would like to update this step > > > to speak directly to the problem this optional step is solving. ------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php _______________________________________________ displaytag-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/displaytag-devel
