Part II. Debugging Routing Contexts

The Camel debugger includes many features for debugging locally and remotely running routing contexts:

  • Setting conditional and unconditional breakpoints on nodes in the route editor
  • Autolaunching the debugger and switching to the Debug perspective
  • Interacting with the running routing context:

    • Switch between breakpoints to quickly compare variable values of message instances
    • Examine and change the value of variables of interest
    • Add variables of interest to the watch list to track them throughout the debug session
    • Disable and re-enable breakpoints on-the-fly
    • Track message flow graphically in the routing context runtime
    • Examine console logs to track Camel and debugger actions

Before you can run the Camel debugger, you must set breakpoints on the nodes of interest displayed on the route editor’s canvas. Then you can run the Camel debugger on a project’s routing context .xml file to find the logic errors in it and fix them. Invoking the Camel debugger runs the routing context in debug mode and opens the Debug Perspective.