iocanel wrote:
> 
> the error you mention usually means 2 things:
> a) either the request is empty.
> b) or you have already read the stream (logging maybe)?
> 

The request is definitely not empty.  The test case I attached previously is
a very simple CXF example where one CXF module calls another using the
cxf-nmr transport, passing a string and getting a string back.  If anyone
has already read the stream and is rereading it, it is the CXF NMR transport
classes.  My test case is based on the two examples included in the
distribution - cxf-nmr and cxf-osgi.  cxf-nmr is pretty much unchanged, and
the cxf-osgi is changed only to insert a <jaxws:client> that is injected and
used to call the endpoint published by cxf-nmr.

-- 
View this message in context: 
http://old.nabble.com/CXF-NMR-transport-%22premature-end-of-file%22-errors-tp28261169p28267014.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.

Reply via email to