I went ahead and added the ability for it to natively support sending any object that implements Serializable. There were several places that were converting the body of the exchange to a byte[] then calling channel.basicPublish(...). I combined all of them into this one method. I'm not a fan of using a try / catch to see if the TypeConverter was able to convert the body to a byte[] but I think it provides the best backwards compatibility and flexibility. I could also make it an endpoint option to always Serialize (defaulted to off).
-- View this message in context: http://camel.465427.n5.nabble.com/Adding-inOut-support-to-the-RabbitMQ-component-tp5764656p5765718.html Sent from the Camel Development mailing list archive at Nabble.com.
