You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@aries.apache.org by "Dominik Przybysz (Jira)" <ji...@apache.org> on 2026/10/03 19:14:01 UTC

[jira] [Closed] (ARIES-1858) Make typed property placeholders compatible with older Camel versions

     [ https://issues.apache.org/jira/browse/ARIES-1858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dominik Przybysz closed ARIES-1858.
-----------------------------------

Closing issues of released artifacts

> Make typed property placeholders compatible with older Camel versions
> ---------------------------------------------------------------------
>
>                 Key: ARIES-1858
>                 URL: https://issues.apache.org/jira/browse/ARIES-1858
>             Project: Aries
>          Issue Type: Improvement
>          Components: Blueprint
>    Affects Versions: blueprint-core-1.10.0
>            Reporter: Grzegorz Grzybek
>            Assignee: Grzegorz Grzybek
>            Priority: Major
>             Fix For: blueprint-core-1.10.1, blueprint-cm-1.3.1
>
>
> ARIES-1298 changed the runtime class of bean registered from {{&#123;http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.x.0}property-placeholder}} and {{&#123;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.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)