Hi Jean-Baptiste, since your mail I wasn't thinking in that direction (setting up a JndiContext on the EJB). So thanks for the input!
I used the Camel EJB component to integrate the EJB in my Camel route. Since both deployments run in same application server (ergo the same JVM) the default JndiContext on the JVM shall be used. At least thats what the documentation says on http://camel.apache.org/ejb.html cite: "/In a real application server you most likely do not have to setup a JndiContext on the EJB component as it will create a default JndiContext on the same JVM as the application server, which usually allows it to access the JNDI registry and lookup the EJBs. However if you need to access a application server on a remote JVM or the likes, you have to prepare the properties beforehand./" ). Even the EJB is found as the call happens. And there is still the type conversion left. Did I missed a critical point whilst this superficial view? Thank you all for your help. And as I stated out: My view is probably to narraw so I appreciate any hint. Sven -- View this message in context: http://camel.465427.n5.nabble.com/TypeConversion-with-JAXB-when-calling-remote-EJB-tp4845064p4852261.html Sent from the Camel - Users mailing list archive at Nabble.com.
