Architects and business analysts typically describe integration problems using visual route diagrams. Diagrams make it easier to see all of the integration points and the paths that data travels between them. Icons denoting different transformations and routing choices can be added to flush out more of the details. Diagrams can be discussed and modified on paper before any code is written.
Developers take the diagrams and attempt to convert them into code. This can be challenging for a number of reasons. One is that the diagram may not map directly to any routing language and the developer will have to fudge the mapping. Another is that coding routes requires developers to learn new languages.
Fuse IDE solves theses problems by making route development a visual exercise. Using standardized icons, based on the icons from Gregor Hohpe and Bobby Woolf's [Enterprise Integration Patterns], developers draw out the route on the canvas. They can show the diagram to the architects or analysts to ensure that the route matches their specifications. Fuse IDE provides property editors for all of the patterns and validates all of the connections between patterns. It then generates the code needed to implement the routes.
Fuse IDE has the following route design features:
graphical interface — Drag and drop integration and mediation components to rapidly connect systems.
imports existing routes — Existing routes defined in XML are imported and modeled on the canvas.
predefined building blocks — Fuse IDE comes complete with all of the defined EIPs.
standard notation — All integration and mediation components use a standard notation making it easy to define and reuse routes.
route validation — Links between nodes are validated before the link is created.
JUnit test wizard — Wizard automatically generates JUnit tests for Apache Camel routes.
 |  |  |
 |
