-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've been wondering about the VM component myself-- as I understand it (and I may be wrong) it relies on classloader visibility for VM endpoints to be visible to other components. Would there be any issues of conflict with the OSGi classloader system there? For example, would VM endpoints in one bundle be visible to other bundles?
- --- A. Soroka Software & Systems Engineering :: Online Library Environment the University of Virginia Library On Apr 13, 2012, at 11:07 AM, Christian Schneider wrote: > Btw. there is also the vm: component which allows you to communicate between > bundles... and of course there always is jms :-) > In fact I always use camel directly in Karaf and have not faced bigger issues > where I would have missed the NMR. > > Christian > > > Am 13.04.2012 16:42, schrieb aj...@virginia.edu: >> I found this to be surprisingly difficult. I was motivated by a raft of >> improvements in Camel 2.9.x, especially better Blueprint support, but I ran >> into lots of package import-export problems and this: >> >> http://fusesource.com/issues/browse/MR-434 >> >> so eventually, I switched to using Camel in Karaf without ServiceMix. >> Luckily, our integration problem was simple enough that I could switch from >> using the NMR to using Camel's SEDA component. I'd like to switch back >> before our integrations get more complex (which they always do {grin}). >> >> Of course, YMMV. >> >> --- >> A. Soroka >> Software and Systems Engineering >> the University of Virginia Library >> >> >> On Fri, Apr 13, 2012 at 10:01 AM, James Carman >> <ja...@carmanconsulting.com>wrote: >> >>> Is it okay to upgrade the existing version of Camel that's bundled >>> with ServiceMix? We would like to upgrade to Camel 2.9.x. If so, >>> what's the easiest way to do so? Do we just have both versions >>> running inside the container? >>> > > > -- > Christian Schneider > http://www.liquid-reality.de > > Open Source Architect > Talend Application Integration Division http://www.talend.com > -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org iQEcBAEBAgAGBQJPjC+yAAoJEATpPYSyaoIkTjIH/1+W7tukGUfaF7LkyV93fgdk rVlk+gxHp04bBwivowc85krFErGb6BLfGUEmUdbN3tbfwNx86MZxkPUFGhZJnBRs aaHSKePdk4/TsGOAx+yYA4edGRlPofGrKCHfJABXyGYuoHiON+H1L8vxh9ziqDVN ti+IyFYxNEQZ4hLiIKyeX8M/F0j4Uu5XXOkVViMrqKXc+8VV8B/Utvc5gG+KKJtU GbK/3kMLYg3KZiF1HqBqw+1LR7I1WYpgEcBMenXyHqrMNOKwskxBTEYDZjtMDIb6 Z/Ad+PN6a735g5G/0O3IwVCsIsEHvnqkNDCbAONNpewzjHD2nK7t7cSQ8oWf/eA= =mMck -----END PGP SIGNATURE-----
