I also would like to see Tapestry check if the response is committed and only set the content type if it isn't. Yes, this is a Weblogic bug, and I'm working the issue with Bea, and yes, a wrapper can work around it; however; it also seems to me to be a good idea to just add this check to Tapestry. There are plenty of Weblogic 8.1 users, and it is harmless to not do the setContentType if the response is already committed... -Tom
-------------------- m2f -------------------- Sent from www.TapestryForums.com Read this topic online here: <<topic_link>> http://www.tapestryforums.com/viewtopic.php?p=12361#12361 -------------------- m2f --------------------
