[ARIES-1858] Make typed property placeholders compatible with older Camel versions

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: blueprint-core-1.10.0
• Fix Version/s: blueprint-core-1.10.1, blueprint-cm-1.3.1
• Component/s: Blueprint
• Assignee: Grzegorz Grzybek
• Reporter: Grzegorz Grzybek
• Created: 08/Nov/18 08:04
• Updated: 08/Nov/18 14:03
• Resolved: 08/Nov/18 13:07

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.

Issue Links

• is related to: CAMEL-12570 Support fixed property placeholders from Aries blueprint
• is related to: ARIES-1298 Support typed configurations in property placeholders
• relates to: KARAF-5776 Upgrade to Aries Blueprint 1.10.1, Blueprint CM 1.3.1, Blueprint Web 1.1.1