I ran into a similar issue this week with my own interceptor which was consuming the stream data. The patch fixed that issue so hope it fixes your issue too
-----Original Message----- From: Gabriel Guardincerri [mailto:[email protected]] Sent: 26 June 2009 18:20 To: [email protected] Subject: RE: Using LoggingInInterceptor makes a JAX-RS proxy clients crash wau.... that's what I call a fast response!!! Thanks!!! I'm using 2.2.2, so no problem there. Eamonn Dwyer wrote: > > Hi Gabriel > Would sounds like you need the patch I put in today > https://issues.apache.org/jira/secure/ManageAttachments.jspa?id=12428957 > > The patch hasn't been approved and applied yet. > > Hope it helps > Eamonn > > > -----Original Message----- > From: Gabriel Guardincerri [mailto:[email protected]] > Sent: 26 June 2009 17:43 > To: [email protected] > Subject: Using LoggingInInterceptor makes a JAX-RS proxy clients crash > > > Hi, > > We are using a JAX-RS proxy client to invoke servicies. We are using the > default data binding (JAXB). And when we turn on the > LoggingInInterceptor we > get this error > > "JAXBException occurred : Premature end of file." > > Debugging a little we notice that CXF tries to parse the xml using an > Inputstream, and we suppose that it was already consumed by the > LoggingInInterceptor, so that's way there is nothing more to read, and > the > parser gets an end of file. > > Should I create a jira issue? > -- > View this message in context: > http://www.nabble.com/Using-LoggingInInterceptor-makes-a-JAX-RS-proxy-cl > ients-crash-tp24223626p24223626.html > Sent from the cxf-user mailing list archive at Nabble.com. > > > -- View this message in context: http://www.nabble.com/Using-LoggingInInterceptor-makes-a-JAX-RS-proxy-cl ients-crash-tp24223626p24223916.html Sent from the cxf-user mailing list archive at Nabble.com.
