Re: Wiretap adds exchanges to MockEndpoint used in NotifyBuilder expression.

OK. I guess I was thinking about it such that a wiretap is like a tee where the new exchange isn't part of the current route, so I didn't expect it to end up in the mock for the route. I worked around it by using a filter. Something like: NotifyBuilder notify = new NotifyBuilder(context)

Wiretap adds exchanges to MockEndpoint used in NotifyBuilder expression.

My understanding is that normally you can test a route by using the NotifyBuilder and a MockEndpoint and if you send one message into the route, you should be able to satisfy the mock.expectedMessageCount(1). However, it appears that the use of the wiretap component in a route adds extra

Re: AutoMocking not working with Blueprint?

2.14.0 worked. But I'm testing for bundles that eventually are to be run on jboss-fuse-6.0.0.redhat-024. -- View this message in context: http://camel.465427.n5.nabble.com/AutoMocking-not-working-with-Blueprint-tp5758319p5758381.html Sent from the Camel - Users mailing list archive at

Re: AutoMocking not working with Blueprint?

2.11.2 works 2.11.1 doesn't -- View this message in context: http://camel.465427.n5.nabble.com/AutoMocking-not-working-with-Blueprint-tp5758319p5758383.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: AutoMocking not working with Blueprint?

camel-version2.10.0.redhat-60024/camel-version activemq-version5.8.0/activemq-version -- View this message in context: http://camel.465427.n5.nabble.com/AutoMocking-not-working-with-Blueprint-tp5758319p5758346.html Sent from the Camel - Users mailing list archive at Nabble.com.

AutoMocking not working with Blueprint?

I get the following error in the testMockAllEndpoints test, but the other two work fine: java.lang.AssertionError: mock://seda:result Received message count. Expected: 1 but was: 0 at org.apache.camel.component.mock.MockEndpoint.fail(MockEndpoint.java:1318) at

Re: Gave up waiting for service dependencies during CamelBlueprintTestSupport test of custom camel component

It turns out that I had an incorrect type of packaging in my pom.xml file. It should have been packagingbundle/packaging instead of 'jar'. This enabled the junit to pass. -- View this message in context:

Gave up waiting for service dependencies during CamelBlueprintTestSupport test of custom camel component

I've created a custom component (talend) which passes its own junit test. I've mvn installed it to my local repo. Now I want to use the component. So I have a separate blueprint project. I have camel.version set to 2.11.2 and the new component as a dependency in this project's pom.xml -

withAdvice mocks all routes, not just first route

I was trying to mock the endpoint that all my test routes funnel into (outPoint) by using adviceWith. The http://camel.apache.org/advicewith.html documentation (at the bottom) has this example: It uses the first object (Route) in the RouteDefinitions collection because it calls get(0). I

Re: MockEndpoint expectedBodiesReceived should handle duplicates

other person. The views and opinions expressed in this email are those of the sender and may not represent the views and opinions of TransCentra. From: Christian Mueller [via Camel] ml-node+s465427n5716367...@n5.nabble.com To: wjmcdonald william.mcdon...@transcentra.com Date: 07/23/2012