Uploaded image for project: 'Camel'
  1. Camel
  2. CAMEL-10127

OsgiDefaultCamelContext should call parent constructor with registry

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 2.17.1
    • Fix Version/s: 2.18.0
    • Component/s: camel-osgi
    • Labels:
      None
    • Estimated Complexity:
      Unknown

      Description

      OsgiDefaultCamelContext constructor doesn't call super to pass registry so inconsistent registries are set in DefaultCamelContext and DefaultCamelContext instances.

      If a client create OsgiDefaultCamelContext with custom registry then (private) variable in DefaultCamelContext is not initialized and a different new instance will be created by getRegistry method.

      Either scope of registry in DefaultCamelContext should be changed to protected or OsgiDefaultCamelContext should pass the reference.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                davsclaus Claus Ibsen
                Reporter:
                borcsokj Börcsök József
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: