Yes mock keeps a copy of the exchange in memory. Though you can use
retainFirst/retainLast option to only keep X number of copies. Read
more about the mock at its website.
On Thu, Jan 23, 2014 at 3:36 AM, contactreji wrote:
> Hi All
>
> I was using mock component as a sink element in one of the
Can you show us please your Camel route ? Have you created a Camel Unit
Test to verify that the mock component receive the camel exchange and that
the info is logged ?
BTW, why do you use mock component instead of a bean, log processors ?
On Thu, Jan 23, 2014 at 3:36 AM, contactreji wrote:
> Hi
Hi All
I was using mock component as a sink element in one of the stubs i had
created representing a destination system.
Once pushed to mock:end, it is not used by any assertions statements /
logic.
*I wanted to know if the exchanges pushed to mock:end component will stay in
memory or is the exc
