Thanks Willem. Then I can leave my configuration as it is. Geert
GEERT VANHEUSDEN SENIOR DEVELOPER Jaarbeurslaan 19 box 11, 3600 Genk, Belgium T +32 (0)89 32 34 80 F +32 (0)89 36 37 95 www.aviobook.aero Product of the AvioVision Company The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, you are kindly requested to notify us immediately by replying to the message and deleting it from your computer.Any views or opinions presented in this email or any attachments are solely those of the author and do not necessarily represent those of AvioVision, or associated companies. On Tue, Sep 23, 2014 at 2:37 PM, Willem Jiang <[email protected]> wrote: > It should be OK to share the components across the camel contexts which is > inside of the same spring application context. > > As camel context look up the component from the registry which delegates to > the spring application to look up the beans by using name. > > > -- > Willem Jiang > > Red Hat, Inc. > Web: http://www.redhat.com > Blog: http://willemjiang.blogspot.com (English) > http://jnn.iteye.com (Chinese) > Twitter: willemjiang > Weibo: 姜宁willem > > > > On September 23, 2014 at 6:23:08 PM, Geert Vanheusden > ([email protected]) wrote: >> Hi, >> >> I have two questions concerning overruling the default http4 component. >> >> Currently I use the following Spring config to override the http4 component: >> >> ----- >> > class="org.apache.http.impl.conn.PoolingHttpClientConnectionManager"> >> >> >> >> >> >> >> >> >> >> > ref="httpClientConnectionManager" /> >> >> ----- >> >> So my first question is, is it possible to provide the following alias >> config in Spring and does it work if I switch to https? >> >> >> >> My second question involves passing the camelContext in the http4 >> component bean definition. As you can see above, I didn't set the >> camelContext because I use multiple camel contexts in my application. >> It seams to work without passing the context but is it ok to do this? >> How is the context set when I don't set it in the bean definition? >> >> Kind regards, >> >> Geert >> >
