Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-4834

"start-level" property in <feature> element and 'start="false"' in <bundle> element didn't work in Fuse 6.2.1

    XMLWordPrintable

Details

    • % %
    • Hide

      1. start Fuse 6.2.1 and create fabric root container and child container.
      2. build "camel-cbr" and "camel-log" project which located in Fuse_Home\quickstart\beginner folder.
      3. create profile and import "features.xml"(attached) to it.
      4. add this profile to root or child container.
      5. "list" command shows:
      ~~~
      [ 239] [Active ] [Created ] [ ] [ 80] JBoss Fuse Quickstart: camel-cbr (6.2.1.redhat-084)
      [ 240] [Active ] [Created ] [ ] [ 80] JBoss Fuse Quickstart: camel-log (6.2.1.redhat-084)
      ~~~
      It shows "camel-log" started automatically even its has 'start="false"', log message can confirm it as well.
      And the start level is "80" not "93" which has set in <feature> element, however it works in <bundle> element like below:
      ~~~
      <bundle start-level="93">...</bundle>
      ~~~

      PATH="/home/pantinor/Desktop/features.xml"
profile-create sample
fabric:profile-edit --repository file://$PATH sample
profile-edit --feature example-camel-bundles sample
container-add-profile root sample
      Show
      1. start Fuse 6.2.1 and create fabric root container and child container. 2. build "camel-cbr" and "camel-log" project which located in Fuse_Home\quickstart\beginner folder. 3. create profile and import "features.xml"(attached) to it. 4. add this profile to root or child container. 5. "list" command shows: ~~~ [ 239] [Active ] [Created ] [ ] [ 80] JBoss Fuse Quickstart: camel-cbr (6.2.1.redhat-084) [ 240] [Active ] [Created ] [ ] [ 80] JBoss Fuse Quickstart: camel-log (6.2.1.redhat-084) ~~~ It shows "camel-log" started automatically even its has 'start="false"', log message can confirm it as well. And the start level is "80" not "93" which has set in <feature> element, however it works in <bundle> element like below: ~~~ <bundle start-level="93">...</bundle> ~~~ PATH= "/home/pantinor/Desktop/features.xml" profile-create sample fabric:profile-edit --repository file: //$PATH sample profile-edit --feature example-camel-bundles sample container-add-profile root sample
    • 6.3 Sprint 2 (1-Feb - 26-Feb)

    Description

      In Fuse 6.2.1 fabric enviroment, if "feature.xml" like below:
      ~~~
      ...
      <feature name="example-camel-bundles" start-level="93">
      <bundle start="false">mvn:a.b.c/camel-log/6.2.1.redhat-084</bundle>
      ...
      </feature>
      ...
      ~~~

      After deploying into fabric container(root or child), bundle "camel-log" will be started automatically and its start-level will shows "80" not "93".

      Attachments

        2. features.xml
          0.3 kB
          xu zhang

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. ENTESB-3780 Some bundles had status changed from "Active" to "Resolved" after fabric was created

          • 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

          Bug - A problem that impairs or prevents the functions of the product. ENTESB-4816 [patching] Fix detection of fabric env when initalizing patch management

          • 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

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) ENTESB-3416 Make sure all bundles are in the Active state by default

          • 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

              pantinor@redhat.com Paolo Antinori
              zhangxu1324_jira xu zhang (Inactive)
              Roman Jakubco Roman Jakubco (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: