work perfectly.
--
View this message in context:
http://camel.465427.n5.nabble.com/Trouble-with-asserts-on-a-mockendpoint-receiving-caught-exceptions-tp5726373.html
Sent from the Camel - Users mailing list archive at Nabble.com.
reason why this is happening?
>
> Note, the asserts I perform on the resultEndpoint work perfectly.
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Trouble-with-asserts-on-a-mockendpoint-receiving-caught-exceptions-tp5726373.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
--
any value, including 0, and the test always passes!
> > Can
> > anybody see any obvious reason why this is happening?
> >
> > Note, the asserts I perform on the resultEndpoint work perfectly.
> >
> >
> >
> > --
> > View this message in context:
> >
> http://camel.465427.n5.nabble.com/Trouble-with-asserts-on-a-mockendpoint-receiving-caught-exceptions-tp5726373.html
> > Sent from the Camel - Users mailing list archive at Nabble.com.
> >
>
>
>
> --
>
gt;> be
>> > the case. If I put a log after the docatch and before the to(errorBin) I
>> > see
>> > the log message.
>> >
>> > However, when I try to do asserts on this it doesn't seem to work. I can
>> > set
>> > expected messages to any value, including 0, and the test always passes!
>> > Can
>> > anybody see any obvious reason why this is happening?
>> >
>> > Note, the asserts I perform on the resultEndpoint work perfectly.
>> >
>> >
>> >
>> > --
>> > View this message in context:
>> >
>> http://camel.465427.n5.nabble.com/Trouble-with-asserts-on-a-mockendpoint-receiving-caught-exceptions-tp5726373.html
>> > Sent from the Camel - Users mailing list archive at Nabble.com.
>> >
>>
>>
>>
>> --
>>
>
>
gt;> >
> >> >
> >> >
> >> > The test data includes some input that throws exceptions so I am
> >> expecting
> >> > those to end up in the mock endpoint called errorBin. This does seem
> to
> >> be
> >> > the case. If I put a log after the docatch and before the
> to(errorBin) I
> >> > see
> >> > the log message.
> >> >
> >> > However, when I try to do asserts on this it doesn't seem to work. I
> can
> >> > set
> >> > expected messages to any value, including 0, and the test always
> passes!
> >> > Can
> >> > anybody see any obvious reason why this is happening?
> >> >
> >> > Note, the asserts I perform on the resultEndpoint work perfectly.
> >> >
> >> >
> >> >
> >> > --
> >> > View this message in context:
> >> >
> >>
> http://camel.465427.n5.nabble.com/Trouble-with-asserts-on-a-mockendpoint-receiving-caught-exceptions-tp5726373.html
> >> > Sent from the Camel - Users mailing list archive at Nabble.com.
> >> >
> >>
> >>
> >>
> >> --
> >>
> >
> >
>