Hi, Is there some documentation around the strategy Camel takes when deciding what to convert the body of an exchange to before sending to an endpoint?
For example, I have set a File object in the body of an exchange and send this to a JMS endpoint. When the exchange is obtained from that endpoint, the body contains a byte array of the contents of the file the File object represents. Given the File object is serializable I expected a File object to be available at the other end. I could just send the File URI string and create a new File object on the other side, but I wondered where/if the conversion strategy for Camel is documented? Cheers, Tom