Since we're on a major migration process of this website, some component documents here are out of sync right now. In the meantime you may want to look at the asciidoc in the repository:

Why is my message empty?

In Camel the message body can be of any types. Some types are safely readable multiple times, and therefore do not 'suffer' from becoming 'empty'.
So when you message body suddenly is empty, then that is often related to using a message type that is no re-readable; in other words, the message
body can only be read once. On subsequent reads the body is now empty. This happens with types that are streaming based, such as java.util.InputStream etc.

A number of Camel components supports and use streaming types out of the box. For example the HTTP related components, and CXF etc.

Camel offers a functionality Stream caching; that caches the stream, so it can be re-readable. By enabling this cache, the message body
would no longer be empty.

© 2004-2015 The Apache Software Foundation.
Apache Camel, Camel, Apache, the Apache feather logo, and the Apache Camel project logo are trademarks of The Apache Software Foundation. All other marks mentioned may be trademarks or registered trademarks of their respective owners.
Graphic Design By Hiram