You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@camel.apache.org by apanday <ap...@apache.org> on 2014/09/18 16:42:19 UTC

testing the tracer

Hi,

I'm writing a "functional tracer" (similar to the jpa tracer example) and i
have two issues

- I'd like to test my traces, independently of the actual DB (a nosql in my
case), so i'm trying to "weave" a mock in place, like:
weaveById("direct:tracer").replace.to("mock:traced")

the route "direct:tracer" exists of course, but when running my test I get
java.lang.IllegalArgumentException: There are no outputs which matches:
direct:tracer in the route

And indeed, the output is not part of the main route; it's an interceptor..
Any way around this?

- second issue: 
in spite of putting explicit IDs to my processors, the trace (using
defaultTraceEventMessage.getToNode) still contains unuseable names such as
"org.apache.camel.scala.ScalaProcessor@5e10a811" 

How could I get the meaningful ID instead?

Thanks



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