Nice work Claus. Occasionally i've also felt the need for easier debugging of
Camel routes (although proper unit- and integration tests help reduce this
issue a lot).
When debugging I think it might be useful for users to call getShortName()
on the provided ProcessorDefinition in beforeProcess() to limit the number
of invocations and quickly find the right processor. For example:
@Override
protected void beforeProcess(Exchange exchange, Processor, processor,
ProcessorDefinition definition) {
if ("transform".equals(definition.getShortName()) {
// place breakpoint in IDE on log statement below
log.info("Body before transformation " +
exchange.getIn().getBody())
}
}
I'll say +1 for including before/afterProcess() methods in CamelTestSupport.
-----
Richard Kettelerij,
http://github.com/rkettelerij
--
View this message in context:
http://camel.465427.n5.nabble.com/DISCUSS-Easier-Camel-route-debugging-from-Camel-Test-Kit-tp3215088p3216041.html
Sent from the Camel Development mailing list archive at Nabble.com.
