Oh two things to mention with respect to my last mail 1) I only sent you a link to the attachment, the jira is actually https://issues.apache.org/jira/browse/CXF-2322
2) I should have also said that the patch was created for CXF 2.2.x so would be easy to apply if you have upgraded to CXF 2.2.2. If you are using an older version maybe you could still try applying it to the code corresponding the version of CXF you are using and then "massage" the code a bit to suit the version of CXF you are using. Regs Eamonn -----Original Message----- From: Eamonn Dwyer Sent: 26 June 2009 17:45 To: '[email protected]' Subject: RE: Using LoggingInInterceptor makes a JAX-RS proxy clients crash 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.
