On 07/09/12 13:57, sireesh wrote:
Sorry to mention that I was not getting any exception in my earlier post. An exception is thrown while JAXBProvider is trying to unmarshal.Caused by: com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog at [row,col {unknown-source}]: [1,0] at com.ctc.wstx.sr.StreamScanner.throwUnexpectedEOF(StreamScanner.java:677) at com.ctc.wstx.sr.BasicStreamReader.handleEOF(BasicStreamReader.java:2104) at com.ctc.wstx.sr.BasicStreamReader.nextFromProlog(BasicStreamReader.java:2010) at com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1102) at com.sun.xml.bind.v2.runtime.unmarshaller.StAXStreamConnector.bridge(StAXStreamConnector.java:160) at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal0(UnmarshallerImpl.java:360) at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:332) at org.apache.cxf.jaxrs.provider.JAXBElementProvider.unmarshalFromInputStream(JAXBElementProvider.java:214) at org.apache.cxf.jaxrs.provider.JAXBElementProvider.doUnmarshal(JAXBElementProvider.java:180) at org.apache.cxf.jaxrs.provider.JAXBElementProvider.readFrom(JAXBElementProvider.java:149) Did anyone hit this problem earlier? If so, can you please post how you got through this issue.
Looks like no response payload is coming back. Can you add a logging feature on the client side ? Also check custom stream readers if any Cheers, Sergey
Thanks, Kiran Sireesh -- View this message in context: http://cxf.547215.n5.nabble.com/Unable-to-unmarshal-REST-response-into-POJO-tp5713694p5713695.html Sent from the cxf-user mailing list archive at Nabble.com.
