If I have an existing web service that I need to create a client for, transform the information, then pass it on to another webservice (after heavy data manipulation and changes in format) it seems like POJO would be ideal, at least for the first two pieces.
It is my understanding that the client could be a java bean that is originated on a timer, and it could pass the message as a POJO to another bean which would be expecting that obejct to do the transformation. Once the transformation is complete the route could continue to a CXF endpoint for the end service in either POJO or MESSAGE format, depending on how I wrote the return type on the exchange for the transformation. It does seem like there are a large amount of ways of doing the same thing with Camel, which is amazingly powerful, but also sort of overwhelming to a newbie like myself with it. Thats why I am just trying to understand what the true pieces are that I should focus on. -- View this message in context: http://camel.465427.n5.nabble.com/Type-Conversion-Question-tp4995814p5001373.html Sent from the Camel - Users mailing list archive at Nabble.com.
