Overrule default http4 component

Hi, I have two questions concerning overruling the default http4 component. Currently I use the following Spring config to override the http4 component: - - So my first question is, is it possible to provide the fol

Re: Overrule default http4 component

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

direct-vm mocking bug

Hi Guys, I wanted to mock a "direct-vm" endpoint with the "block=true" option but it fails. Here you can find a unit test to reproduce this: === import org.apache.camel.builder.RouteBuilder; import org.apache.camel.component.mock.MockEndpoint; import org.apache.c

Re: direct-vm mocking bug

Any thoughts on this issue or should I just create a ticket for it? Kind regards, Geert On Tue, Nov 4, 2014 at 11:13 AM, Geert Vanheusden wrote: > Hi Guys, > > I wanted to mock a "direct-vm" endpoint with the "block=true" option > but it fails. > > Here

Re: direct-vm mocking bug

ar exp to match using wildcards etc. > > On Thu, Nov 6, 2014 at 9:10 AM, Geert Vanheusden > wrote: > > Any thoughts on this issue or should I just create a ticket for it? > > > > Kind regards, > > > > Geert > > > > On Tue, Nov 4, 2014 at 11:13 AM,

Closed (removed) StreamCache when doing a Wiretap

Hi, I noticed a bug where the body (StreamCache) was already removed before the exchange reached the end (in the Wiretap route). I found the following ticket https://issues.apache.org/jira/browse/CAMEL-8386 and code https://fisheye6.atlassian.com/changelog/camel-git?cs=4661cbb94513d6047e58581b23d

Re: Closed (removed) StreamCache when doing a Wiretap

s finished. The wire tap runs in a separate thread and > therefore it can happen that it tries to read the cached file when it > is already deleted, especially when you have a delay in the wiretap > route ("direct:x"). > > > Regards Franz > > On Fri, Apr 17, 2015 at 6:05

Re: Closed (removed) StreamCache when doing a Wiretap

; >> return copy; > >> } > >> > >> The idea behind this is to make a copy of the stream cache file, so > >> that you get an additional stream cache file for the second route (in > >> your case for the route "direct:x"). This second stre

Re: Closed (removed) StreamCache when doing a Wiretap

t;> // set MEP to InOnly as this wire tap is a fire and forget > >>> copy.setPattern(ExchangePattern.InOnly); > >>> return copy; > >>> } > >>> > >>> The idea behind this is to make a copy of the stream

Re: Closed (removed) StreamCache when doing a Wiretap

gt; IOHelper.close(streamCache, cos); > >>>> streamCache.reset(); > >>>> } > >>>> copy.getIn().setBody(cos.newStreamCache()); > >>>> } > >>>> // s