i think something is consuming the payload stream somewhere before your other processing step is trying to consume/convert the data. when using streaming, either you can consume the data once or must convert it to something else if it needs to be consumed again.
CAMEL-8663 is not related to this behavior. 2015-12-02 21:55 GMT+01:00 ychawla <premiergenerat...@gmail.com>: > Hello All, > I added the parameter: allowStreaming=false to the CXF endpoints that were > causing an issue and then they started to work normally. It definitely > seems like a bug because I would send consecutive schema valid messages and > one would fail with the WoodStox exception and the other would not. > > Disabling streaming works but I believe there is a bug with the stream being > sent from CXF to Camel. Maybe it could be related to this JIRA issue: > > https://issues.apache.org/jira/browse/CAMEL-8663 > > In my use case, I need to modify the payload and extract elements from it so > it needs to be converted to a DOM anyway. > > Hopefully this helps the next person who sees this issue. > > However, does anyone know how to set the allowStreaming property globally > for all CXF endpoints? > > Thanks, > Yogesh > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Soap-Body-is-Empty-or-Partial-XML-tp5774364p5774624.html > Sent from the Camel - Users mailing list archive at Nabble.com.
