Hi Matt Just curious, did you get a chance to validate the Jackson provider ? We may still get a chance to track the possible CXF issue down before 2.4.0/2.3.4 is out,
thanks, Sergey On Mon, Mar 21, 2011 at 5:32 PM, Sergey Beryozkin <[email protected]>wrote: > Hi Matt > > On Mon, Mar 21, 2011 at 5:28 PM, Matthew Glubb <[email protected]>wrote: > >> Hi Sergey, >> >> On 21 Mar 2011, at 17:09, Sergey Beryozkin wrote: >> >> > Sorry for a delay. >> >> No problem at all. I appreciate the time. It's one of the few things you >> can never restore to someone. >> >> > indeed :-) > > >> > Do you know if ehcache filters are wrapping the servlet response stream >> ? >> > May be in some specific case the flush() is called on the output stream >> in >> > one of the CXF providers which may be the cause of this exception ? >> >> I believe that they do wrap the response stream. This is to modify the >> headers after a cache miss. In the case of a cache hit we wouldn't get as >> far as the servlet. >> >> I'm using org.codehaus.jackson.jaxrs.JacksonJaxbJsonProvider. I'll look >> into it. >> >> > you may want to try org.apache.cxf.jaxrs.provider.JSONProvider, just to see > if it's anything to do with providers at all... > > >> > If you could open a JIRA and provide a simple maven project for us to >> > test/debug then it can help... >> >> If the providers don't turn up anything I'll do that. >> >> > ok, thanks > > Sergey > > >> Thanks, >> >> >> Matt >> >> >> > -- Sergey Beryozkin Application Integration Division of Talend <http://www.talend.com> http://sberyozkin.blogspot.com
