title: How do you trace/debug Apache Camel or AOP-modified code?
body: <p>I'm trying to debug a webapp using Apache Camel from Eclipse and while I'm 'tracing into' I arrive at a point where Eclipse says that no source file is available and I can see bytecode shown in Eclipse (where usually I see sourcecode) but apparently I cannot advance into that bytecode (I try 'F6 / Step Over' but nothing happens) anyway (not that it would have been that useful compared to source code).</p>
  
  <p>So how are you supposed to trace into such a beast?</p>
  
  <p>I'm wondering if all these code-generating/code-intercepting layers aren't creating more problems than they're trying to solve.  It seems like it's helpful as long as everything works but as soon as there's a problem, things become very hard to diagnose.</p>
  
  <p><strong>EDIT</strong> I don't want to trace Apache Camel <em>itself</em>.  I just want to trace a program that is using Apache Camel and I realize that things quickly gets very messy: basically you kinda lose your tracing ability because you jump from your Java source code to "something".  </p>