Hi Hervé,
no, as in Karaf, Camel register all context as OSGi services.
Regards
JB
On 01/24/2012 01:01 PM, Hervé BARRAULT wrote:
Hi,
thanks for answer.
Does it means, put camel-core.jar in lib directory when using it in Karaf ?
Regards
Hervé
On 1/24/12, Jean-Baptiste Onofré<j...@nanthrax.net> wrote:
Hi Hervé,
VM component extends the SEDA component.
The difference is that the BlockingQueue is in the classloader tree
containing the camel-core.jar (system classpath).
No impact on performance.
Regards
JB
On 01/24/2012 11:34 AM, Hervé BARRAULT wrote:
Hi,
i have seen that there is too closed component which are SEDA and VM
component.
The difference is a SEDA component can communicate only in a camelContext.
Is there some performance consideration ?
Is it better to use multiple SEDA component in one camel context or
use multiple VM component across different camel context ?
Regards
Hervé
--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
