WireTap creates a new exchange that is the purpose of it http://camel.apache.org/wire-tap
On Fri, Nov 14, 2014 at 8:21 AM, wjmcdonald <william.mcdon...@transcentra.com> wrote: > 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 > exchanges - see attached java test and xml. > > TestWiretapNotifySpring.java > <http://camel.465427.n5.nabble.com/file/n5759085/TestWiretapNotifySpring.java> > WiretapNotifySpring.xml > <http://camel.465427.n5.nabble.com/file/n5759085/WiretapNotifySpring.xml> > WiretapNotifyTestResults.txt > <http://camel.465427.n5.nabble.com/file/n5759085/WiretapNotifyTestResults.txt> > > Is this working as designed or a bug? Is there a way to filter the extra > ones out? How would I test such a route that includes various wiretap > elements? I'd also like to test attributes (like MyHeader) on just the > expected route, not the extra exchanges. > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Wiretap-adds-exchanges-to-MockEndpoint-used-in-NotifyBuilder-expression-tp5759085.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen hawtio: http://hawt.io/ fabric8: http://fabric8.io/
