camel-jaxb just provides type convert as a fallback converter, it is last thing camel converter can do. The exception will be thrown, if the camel-jaxb data format can't convert the XML to the type you want.
Using the Message Translator EIP can give you full control of the whole process. -- Willem Jiang Red Hat, Inc. FuseSource is now part of Red Hat Web: http://www.fusesource.com | http://www.redhat.com Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/) (English) http://jnn.javaeye.com (http://jnn.javaeye.com/) (Chinese) Twitter: willemjiang Weibo: willemjiang On Tuesday, October 16, 2012 at 2:17 AM, javendo wrote: > Hi, I could resolve my problem. > > I have made a mistake when I sent messages with different XML structures in > the body. The jaxb could not identify (and I am not helping it) how to > unmarshal the xml. I applied the Message Translator EIP using a processor > that knows how to deal with the different XML. > > []s > > Alessandro > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Unmarshalling-stop-working-tp5720946p5721069.html > Sent from the Camel - Users mailing list archive at Nabble.com > (http://Nabble.com).
