BufferedResponseWrapper doesn't extend HttpServletResponseWrapper because the wrapper can also be used on j2ee 1.2 appserver. While the filter itself can be used only on j2ee 1.3 application servers, the response wrapper can successfully be used, together with a servlet, on older appserver.
Actually there are no instructions on how to set up a servlet for export, but there are a couple of junit tests showing how a servlet could take the place of the response filter. So I'll prefer keeping this class backward compatible, but if extending HttpServletResponseWrapper is the only way to make Weblogic happy I can add to cvs the 2 different implementation (and use the new one in the filter)... fabrizio ----- Original Message ----- From: [EMAIL PROTECTED] <[EMAIL PROTECTED]> Date: Mon, 26 Jul 2004 17:31:25 +1000 Subject: RE: [displaytag-devel] patch for BufferedResponseWrapper To: [EMAIL PROTECTED] yep - fine by me. I did a small amount of research into why it wasn't done this way in the first place but didn't find anything. I'm interested to hear the reason (its obviously been a conscious decision). An alternative might be to have the response wrapper used be configurable at the filter level - providing for both cases. If it comes back that there's a reason the current patch doesn't suit then I'll do that - marginally more complicated, but would keep us all happy. cheers dim ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click _______________________________________________ displaytag-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/displaytag-devel
