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

Unable to deploy simple project created by Fuse Project wizard to Fuse server

    XMLWordPrintable

Details

    • Hide

      Required elements:

      • A JBDS installation with Fuse tooling installed
      • A configured Fuse 6.2.1 runtime instance (could be installed via the tooling but would need the ../etc/users.properties file updated to add the admin/admin user)
      • A configured server in the Servers view pointing to the runtime instance

      Steps:

      1. Create a new Fuse project with the Blueprint archetype (New->Fuse Project). Use defaults wherever possible.
      2. Start the server in the Servers view.
      3. Add the new Fuse project to the Servers view.
      Show
      Required elements: A JBDS installation with Fuse tooling installed A configured Fuse 6.2.1 runtime instance (could be installed via the tooling but would need the ../etc/users.properties file updated to add the admin/admin user) A configured server in the Servers view pointing to the runtime instance Steps: Create a new Fuse project with the Blueprint archetype (New->Fuse Project). Use defaults wherever possible. Start the server in the Servers view. Add the new Fuse project to the Servers view.

    Description

      While doing some testing of the Getting Started process for the Camel editor/Fuse tooling, I hit upon a few issues with deploying default projects created by the Fuse Project wizard. Some of this may become moot as the new Camel Project wizard comes into its own, but these issues should still hold true there as well.

      The goal for ease-of-use and a smooth getting started experience is to ensure that the user can configure a server in the Servers view, create a new Fuse Project, and deploy it and see it running.

      Following the repro steps, I was unable to successfully deploy the project to the server and interact with it.

      Attachments

        Issue Links

          is incorporated by

          Bug - A problem that impairs or prevents the functions of the product. FUSETOOLS-2018 Cannot directly deploy SwitchYard project into Fuse on Karaf

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed
          relates to

          Bug - A problem that impairs or prevents the functions of the product. FUSETOOLS-1551 Cannot run as Local Camel Context (camel-blueprint)

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              Unassigned Unassigned
              bfitzpat_rh Brian Fitzpatrick (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: