servicemix-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Willem Jiang <>
Subject Re: Large(ish) message issue (CXFBC and Camel)
Date Mon, 31 Jan 2011 12:34:34 GMT
On 1/29/11 10:16 AM, Freeman Fang wrote:
> On 2011-1-29, at 上午8:52, Scott Came wrote:
>> Willem:
>> Hopefully this will be addressed at some point? Are you suggesting
>> that Servicemix 4 won't support accessing Camel SUs via JBI?
> SMX4 support JBI, so the jbi camel su still works, you can take a look
> at camel example shipped with kit.
>> I really would like to use JBI for my application, to take advantage
>> of the NMR. I don't see how I would do that if I deployed the Camel
>> route in a bundle.
> However use camel route bundle directly, you still can take advantage of
> the nmr, as smx4 provide a camel-nmr[1] component, which let you use nmr
> in your camel router directly, you needn't JBI stuff in this cas. You
> can take a look at camel-nmr and cxf-camel-nmr examples shipped with
> smx4 kit.
> [1]
> Freeman
>> I did rebuild the Camel service engine as part of my build from
>> source, so I would expect that everything would pick up the latest
>> version of Camel.

Camel 2.6.0 is released, can you updated the servicemix to pick up it 
and run the test?

>> Thanks.
>> --Scott
>> -----Original Message-----
>> From: Willem Jiang []
>> Sent: Thursday, January 27, 2011 4:06 AM
>> To:
>> Subject: Re: Large(ish) message issue (CXFBC and Camel)
>> Hi Scott
>> I just realize you were using the old JBI stuff.
>> As you are using ServiceMix 4.x, I suggest you put the camel route
>> into a bundle instead create a Camel Service Engine SU for the route.
>> As the Camel Service Engine also have a lib which has the camel-core
>> and camel-spring, I'm not sure it cause the issue that you met.
>> Willem

Blog: (English)
Twitter: willemjiang

View raw message