Uploaded image for project: 'Aries'
  1. Aries
  2. ARIES-1858

Make typed property placeholders compatible with older Camel versions

    XMLWordPrintableJSON

    Details

      Description

      ARIES-1298 changed the runtime class of bean registered from {http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.x.0}property-placeholder and {http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.x.0}property-placeholder. This is definitely not caught by semver plugin.

      camel-blueprint (see CAMEL-12570) added support for this new runtime class - it was needed because Camel explicitly casts and uses reflection on old org.apache.aries.blueprint.ext.AbstractPropertyPlaceholder class, while blueprint-core 1.10.0 registers placeholder class that extends org.apache.aries.blueprint.ext.AbstractPropertyPlaceholderExt - and these two are not related.

      The problem is that when user will try to upgrade to e.g., Karaf with blueprint-core 1.10.0 without upgrading Camel, Camel blueprint will stop detecting blueprint property resolvers.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                gzres Grzegorz Grzybek
                Reporter:
                gzres Grzegorz Grzybek
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: