Hi, As already discussed :), your issue is relative to Camel.
I'm preparing a test case to try to reproduce the issue and check if it's already present on 4.4-SNAPSHOT.
Regards JB On 04/03/2011 08:26 PM, geaaru wrote:
Hi at all, I'm not a smx developer, but an user and I hope that my comment will help decision for next release. I'm currently used yet an old smx version create from a commit of the smx-4.3.0-snapshot with module 2010.10 because new smx-4.3.0 is it very unstable at least in my case where i use a lot camel and camel-jbi component. Currently it isn't possible do: - a restart of a sa with servimix-camel that use from("jbi:endpoint...") - deploy a blueprint camel route with jbi destination (.to("jbi...")) or jbi endpoint. I don't known if that components will be maintained but if yes are in this moment unusable and i think that before next release this bug must be closed. Thanks for read my messagge. Good work at all. Geaaru ----- Original message -----Hi all, The CXF team has made a lot of improvements around OSGi and especially Blueprint. They plan to release CXF 2.4.0 soon (in the following weeks). I think it could have sense to use CXF 2.4.0 for ServiceMix 4.4.0. It means that ServiceMix 4.4.0 will ship: - Karaf 2.2.0 (maybe 2.2.1 at least to have a fix on the zip archive, even if we can fix it in ServiceMix itself) - ActiveMQ 5.5.0 (already done) - Camel 2.7.0 (already done) - CXF 2.4.0 WDYT ? Regards JB
