Re: Append endpoint to route at test-time.

+1 2011/5/9 Claus Ibsen > On Sun, May 8, 2011 at 1:44 PM, Tarjei Huse wrote: > > Hi, > > > > I got a route like this: > > from(bookKeeperQueue).routeId("BookKeeperRoute") > >.process(new BookKeeperProcessor(bookKeeper)); > > > > That I would like to test by appending a mock endpoint

Re: Conceptual 'correctness' of using Camel Unit Tests

Hi Okay we got an improvement in testing time now Before: 3h2m https://hudson.apache.org/hudson/job/Camel.trunk.fulltest/276/ After: 2h28m https://hudson.apache.org/hudson/job/Camel.trunk.fulltest/276/ So we cut down the time with: 34m. Which is roughly 20% Also the assembly part we cannot imp

Re: Append endpoint to route at test-time.

On Sun, May 8, 2011 at 1:44 PM, Tarjei Huse wrote: > Hi, > > I got a route like this: > from(bookKeeperQueue).routeId("BookKeeperRoute") >            .process(new BookKeeperProcessor(bookKeeper)); > > That I would like to test by appending a mock endpoint to the route and > avaiting for it to rece

Aggregator ignore messages after timeout

Hi there, We are attempting to implement an aggregator to implement rules around preferring messages from one source over another with a timeout. We have two message sources A and B which are implemented over two physical networks, and the quality of source A is better than B. So we have these b

Re: Append endpoint to route at test-time.

yep, just use http://camel.apache.org/advicewith.html http://camel.apache.org/advicewith.html and interceptor to decorate with a mock endpoint that you can assert against... tarjei wrote: > > Hi, > > I got a route like this: > from(bookKeeperQueue).routeId("BookKeeperRoute") > .pr

Re: bean, ejb etc... how to set parameters

i did a poc, i need a modification in camel-core, here is the diff: Index: src/main/java/org/apache/camel/component/bean/BeanInfo.java === --- src/main/java/org/apache/camel/component/bean/BeanInfo.java (révision 1100337) +++ src/mai

Re: Necessity of transactional JMS component

On Sat, 07 May 2011 17:54:11 +0300, Hanson wrote: I just wonder what's the necessity of declaring a JMS component as transactional basically. If not, when a JMS to JMS route fails, will the message got lost, in case I have a DefaultErrorHandler and set redelivery attempts to -1? What about a Fi

Append endpoint to route at test-time.

Hi, I got a route like this: from(bookKeeperQueue).routeId("BookKeeperRoute") .process(new BookKeeperProcessor(bookKeeper)); That I would like to test by appending a mock endpoint to the route and avaiting for it to receive the message. I could add a .to(log:something) at the

Re: Camel route stops sending messages

Most of the messages are flowing to splunk fine. A few are failing to get through - possibly we are flooding splunk - hence those errors. But what I dont understand is why the process then stops processing any more messages. On Sun, May 8, 2011 at 6:07 AM, Filippo Balicchia wrote: > Does your sp

Re: bean, ejb etc... how to set parameters

Hi, maybe another solution to this problem could be to add a kind of descriptor file: in camel a bean can extract parameters from headers or something else with annotations, if there is a file saying the same thing the bean could not use any camel imports but do the same. what do you think of a