Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (athena.apache.org: local policy includes SPF record at
 spf.trusted-forwarder.org)
Date: Wed, 13 Nov 2013 01:21:15 -0800 (PST)
From: cristisor <cristisor_ac@yahoo.com>
To: users@camel.apache.org
Message-ID: <1384334475270-5743163.post@n5.nabble.com>
Subject: onCompletion not triggerd in testing
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hello,

I am using the following route:

    protected void createRoute(Processor processor) {
        from(getInputEndpoint())
                .onCompletion()
                .onCompleteOnly()
                .onWhen(customPredicate)
                .process(syncProcessor)
                .end()
                // the onCompletion callback ended and normal processing is
back
                .choice()
                .when(customPredicate)
                .process(syncProcessor)
                .otherwise()
                .process(processor)
                .to(getOutputEndpoint())
                .end();
    }


and I need to do some processing inside the syncProcessor when some other
messages have completed successfully. In deployment environment the route
works fine but the unit tests are always failing because
".process(syncProcessor)" is never triggered.

This is the outputEndpoint:
@EndpointInject(uri = "mock:output")
protected MockEndpoint resultEndpoint;


Could it be that the "mock:output" is not triggering the onCompletion event?

Thanks,
Cristian.


--
View this message in context: http://camel.465427.n5.nabble.com/onCompletion-not-triggerd-in-testing-tp5743163.html
Sent from the Camel - Users mailing list archive at Nabble.com.