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

Unify a logic for processing the bean property 'scope'

XMLWordPrintable

    • Hide
      All new Global Beans, whether the Camel configuration uses the Spring or Blueprint XML DSL, are given the default scope of "singleton" now. The default was already set behind the scenes, but by explicitly setting it in the configuration we avoid an extra update when editing the new bean in the editor.
      Show
      All new Global Beans, whether the Camel configuration uses the Spring or Blueprint XML DSL, are given the default scope of "singleton" now. The default was already set behind the scenes, but by explicitly setting it in the configuration we avoid an extra update when editing the new bean in the editor.

      By default a bean is created without the property 'scope' such as

      <bean class="aaa.HelloBean" id="helloBean"/>

      but once we select the bean and open Properties view then the property is added as follows

      <bean class="aaa.HelloBean" id="helloBean" scope="singleton"/>

      Moreover, the editor is set as dirty and must be saved. This also happens if we import an existing project which contains a bean without any scope.

      I suspect that it is caused by the combo box in Properties view which contains which automatically sets the default value. Is it possible to not add such property whenever we edit it via Properties view?

      If not then please automatically add the property to all newly created beans.

              bfitzpat_rh Brian Fitzpatrick (Inactive)
              apodhrad@redhat.com Andrej Podhradsky
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: