Details
-
Bug
-
Status: Resolved
-
Blocker
-
Resolution: Fixed
-
3.2.2
-
None
Description
Please see: http://www.nabble.com/XStream-with-JBI-td20129124s22882.html
This is due to the limitation imposed by the JbiExchange class, since its messages can only be NormalisedMessage objects, which in turn can only have XML Bodies.
This is issue blocks development with many Camel components, such as XStream, iBATIS, or, in general, any component that requires a Java Object, CSV file, etc. instead of XML to operate.