Hi Sergey, Thanks for the reply, you are probably right and this has nothing to do with CXF. I personally think there is something with some buffered output stream in WebSphere's bowels causing this especially since it works in Tomcat just fine. I don't think it's the JAXB/Stax interaction causing it, some buffer is never being flushed I think. The only thing I thought it could have been from a CXF perspective, was potentially some interceptor (I'm using only defaults) or the CXF servlet itself doing something with the output for a service method that returns void. I've got the source and started tracing through CXF code to see if I can see it do anything that would cause it to somehow intercept the response and wipe it out. Something somewhere up the chain is grabbing the response writer I believe. I'll let you know if I find anything CXF specifc.
Thanks John This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail.
