On Wed Nov 16 23:13:11 2011, Castyn wrote:
Makes sense, thanks. This is all still very new to me, so I wasn't sure what
the trade off and differences were between POJO and MESSAGE (and PAYLOAD).
This was more of a small test. Realistically the jetty endpoint is going to
be replaced with a longer camel route which will originate from a timed pull
of another web service and then be converted to the appropriate message
format. When that happens should I still be using message or should I use
POJO and write the custom marshalling?
It depends on how you deal with the message.
If you just want to do some XML transformation, the MESSAG data format
could be your first choice.
If you want to deal with message body with normal java object, POJO
data format meets you needs.
If you want to build the route with your custom processor, camel
supports it :)
BTW,
You can use the camel-soap to deal with the soap message directly
without using CXF.
--
View this message in context:
http://camel.465427.n5.nabble.com/Type-Conversion-Question-tp4995814p4998015.html
Sent from the Camel - Users mailing list archive at Nabble.com.
--
Willem
----------------------------------
FuseSource
Web: http://www.fusesource.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.javaeye.com (Chinese)
Twitter: willemjiang
Weibo: willemjiang
