I am afraid.
First, since I would have to manually provide the XmlRootElement annotation
to an JAXB generated type and
second, I would probably lose the possibility that the type might be used
within other schemas.
--
View this message in context:
http://camel.465427.n5.nabble.com/TypeConversi
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
.
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 JndiCo
Hi Claus,
thanks for your answer. You are pretty well dedicated in this forum!
I am using Glassfish V3.1.1 with EJB V3.0, as you already assumed correctly.
I stated at Willem within my last post: it is possible to call the "remote"
EJB via an alternative EJB call (in my case from a Servlet refer
Hi,
if I get Willem's point right, I would NOT be able to call the EJB remotely
in either way (using camel ejb or any ordinary ejb invocation mechanism).
But I can perfectly do that, when running a Servlet (in the same deployment
artifact as the camel route is located), injecing it the (remote) E
Hi Claus,
I am using Camel V2.8.1.
The full Stacktrace (with tracing turned on) is as follows:
Thx for your help.
Sven
--
View this message in context:
http://camel.465427.n5.nabble.com/TypeConversion-with-JAXB-when-calling-remote-EJB-tp4845064p4848644.html
Sent from the Camel - Users mailin
Hi,
I already did that (ensured types are compatible making the types
Serializable and setting a proper serialVersionUID). Using the same type
reference on a single deployment works fine as stated out before.
Additionaly, I wrote a TypeConverter that was just casting the inExchange to
the same ty
Hi,
I'am running a route wich perfoms JAXB unmarshalling before calling an EJB:
The camel route and the EJB reside in two different web archives, both
deployt on the same application container.
This results in:
The EJB method expects an object of the same type that was unmarshalled:
When dep
