Hi,
Thanks for the quick reply. I am using 1.2.0.
I have simplified things greatly & I am still getting null.
So on one end, I am sending to through JMS, on the other:
context.addRoutes(new RouteBuilder() {
public void configure() {
// set up a listener on the file component
from("test-jms:queue:PA").process(new Processor() {
public void process(Exchange e) {
Object obj = e.getIn().getBody();
System.out.println("OBJ IS: "+obj);
}
});
}
});
I don't believe I am using the 'camel-cxf' component. I am just using some
cxf generated objects (no need to hit an endpoint yet, that would be several
steps later). So it might be ActiveMQ making it null, but I don't know. I
guess I need a little direction so I can determine where it is being
dropped.
Thanks in advance.
willem.jiang wrote:
>
> Hi ,
>
> Which version of Camel that you use ?
> Can you show me your router configuration code ?
> We just fixed some bugs of the camel-cxf component , The recent fix is
> CAMEL-286[1]
>
> [1] https://issues.apache.org/activemq/browse/CAMEL-286
>
> Willem.
>
> sub3 wrote:
>> Hi,
>> I am just starting to learn camel. I seem to be routing/sending simple
>> objects fine. As soon as I start to use objects generated by cxf's
>> wsdl2java, they come across as null.
>>
>> What is it about these objects that cause this, and is there a way to
>> stop
>> it? I can only assume it has something to do with the way it gets
>> serialized.
>>
>> Thanks for any help.
>>
>
>
>
--
View this message in context:
http://www.nabble.com/Camel---Sending-CXF-generated-objects-tp14989933s22882p14990116.html
Sent from the Camel - Users mailing list archive at Nabble.com.
