When debugging a route it is helpful to see how a test message changes as it passes through a route. It is also helpful to be able to trace the message's path through the route.
Fuse IDE's route tracing feature allows you to do both. The Diagram View displays a visual representation of the route that allows you to walk the route. The Messages View displays the messages processed by the node selected in Diagram View. You can also display the full contents of a message in the Properties viewer.
The advantage of debugging a route in the Fuse perspective is that it allows you to see how the route functions in its actual deployment environment. The route is hooked up to live endpoints that are managed by live brokers. When you drag a test message on to a route's endpoint, you are dropping it onto an actual endpoint and not an in memory entity that stands in for the endpoint.
You can ensure that the start endpoint is properly configured to receive messages. As the message passes through each processor in the route, you can check the entire message including all of the transport headers to see if it is being processed correctly. You can also check that the target endpoint is properly configured to pass the result to the proper destination.
Diagram View displays your routes as graphs. Each node of the graph represents a step in the route and is identified by an icon representing the EIP pattern the node represents.
When route tracing is activated, you can inspect the message that each node has processed by selecting the node from the graph.
 |  |  |
 |
