On Mon Oct 10 14:53:37 2011, smythewin wrote:
Hi,
I investigated a little further on this conversion issue between a camel
artifact and an ejb artifact deployt on the same container.
> From this I can state two thing:
1. deploying the camel route as a dependency of the web archive works fine.
Tthis would have satisfy Willem.Jiang's remark
...but...
2. When annotating the exchange type with
@javax.xml.bind.annotation.XmlRootElement the cast is done as expected! Even
deploying the camel route seperatly. And even without making the types
serializable.
So I'am not a JAXB-Camel guru, but may someone has an idea what is going on
under the hood? Why does the deployment of camel route and the EJB within
the same deployment unit work without the annotation XmlRootElement but the
"remote" call will make the annotation mandatory for type conversion?
Interesting.
camel-jaxb has a fall back converter to be used when the object is
annotated with XmlRootElement.
I'm just guessing there are some magic happen there :)
Thanks for your support.
Sven
--
View this message in context:
http://camel.465427.n5.nabble.com/TypeConversion-with-JAXB-when-calling-remote-EJB-tp4845064p4887193.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
