Uploaded image for project: 'Fuse Tooling'
  1. Fuse Tooling
  2. FUSETOOLS-1211

Adding another route to a Fuse Project doesn't work properly

    XMLWordPrintable

Details

    • Hide

      I tried to add a second route to my blueprint CBR route (a copy of the CBR example route supplied with the camel-spring archetype) that retrieves a message from the 'file:target/messages/undelivered' dir and routes it to another file:target/messages/ <directory>.

      1. With the original route displayed in Design View, open the Route menu (menubar) and select Add Route.
      The Route Editor presents a clean canvas.
      2. Configure the 2nd Route with id=Route2
      3. Drag two endpoint EIPs and one log EIP to the canvas.
      4. Configure the first endpoint to be the consumer (file:target/messages/undelivered), the second endpoint to be the producer (file:target/messages/<anotherDirectory), and the log file (id='log3') to log the passage between the two endpoints.
      5. Connect the nodes together: 1st endpoint=>log3==>2nd endpoint.
      6. Click File>Save All
      7. In Route menu, switch back to Original route, and set its id=Route1.
      8. Click File>Save All
      9. In Route menu, click Route2.
      The canvas continues to display Route1, but Outline View displays Route2 beneath Route1. And if you click a Route2 node there, the Property Editor displays the properties for the selected Route2 node, which you can then edit. But you cannot get the Route Editor to display Route2.

      The altered project (with route1 and route2) runs successfully as a Local Camel Context (without Tests).

      Show
      I tried to add a second route to my blueprint CBR route (a copy of the CBR example route supplied with the camel-spring archetype) that retrieves a message from the 'file:target/messages/undelivered' dir and routes it to another file:target/messages/ <directory>. 1. With the original route displayed in Design View, open the Route menu (menubar) and select Add Route. The Route Editor presents a clean canvas. 2. Configure the 2nd Route with id=Route2 3. Drag two endpoint EIPs and one log EIP to the canvas. 4. Configure the first endpoint to be the consumer ( file:target/messages/undelivered ), the second endpoint to be the producer ( file:target/messages/ <anotherDirectory), and the log file (id='log3') to log the passage between the two endpoints. 5. Connect the nodes together: 1st endpoint=>log3==>2nd endpoint. 6. Click File>Save All 7. In Route menu, switch back to Original route, and set its id=Route1. 8. Click File>Save All 9. In Route menu, click Route2. The canvas continues to display Route1, but Outline View displays Route2 beneath Route1. And if you click a Route2 node there, the Property Editor displays the properties for the selected Route2 node, which you can then edit. But you cannot get the Route Editor to display Route2. The altered project (with route1 and route2) runs successfully as a Local Camel Context (without Tests).

    Description

      After adding a new route to the project, it will not display in the Route Editor's Design View. The original route continues to display on the canvas regardless of whether you use the Route menu on the menu bar to switch to the 2nd route or you click on the 2nd route's icon in outline view. If you click on the 2nd route's icon in outline view, the Property Editor displays the properties for whatever node you select in Outline View, and you can edit them. But you cannot display or modify the 2nd route on the Route Editor's canvas.

      Attachments

        1. FTtwoRoutes111014.log
          595 kB
        2. Route2runs.png
          Route2runs.png
          340 kB
        3. Rte2OutlineView.png
          Rte2OutlineView.png
          57 kB
        4. Rte2RouteMenu.png
          Rte2RouteMenu.png
          16 kB
        5. TwoRouteCamelContext.png
          TwoRouteCamelContext.png
          90 kB

        Activity

          People

            lheinema@redhat.com Lars Heinemann
            jmurphey_jira Jane Murphey (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: