[
https://issues.apache.org/jira/browse/CAMEL-12570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16509323#comment-16509323
]
Grzegorz Grzybek commented on CAMEL-12570:
------------------------------------------
[~ancosen], [~gnt], [~jbonofre], with this fix, Camel will work with
blueprint.core 1.10.0, *but* if we upgrade Karaf 4.2.1 to blueprint.core 1.10.0
/ blueprint.cm 1.3.0, existing Camel applications will stop working (expecting
{{org.apache.aries.blueprint.compendium.cm.CmPropertyPlaceholder}} to be
derived from {{org.apache.aries.blueprint.ext.AbstractPropertyPlaceholder}} and
not from new {{org.apache.aries.blueprint.ext.AbstractPropertyPlaceholderExt}}).
The only backward compatible change I can think of is to have (in blueprint.cm
1.3.1):
* org.apache.aries.blueprint.compendium.cm.CmPropertyPlaceholderExt and
* org.apache.aries.blueprint.compendium.cm.CmPropertyPlaceholder
Which instance should be created by
{{org.apache.aries.blueprint.compendium.cm.CmNamespaceHandler#parsePropertyPlaceholder()}}
should actually depend on XSD of
{{http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.\*}} version used -
existing (before blueprint.core 1.10.0) cm XSD versions should fallback to
{{CmPropertyPlaceholder}} derived from {{AbstractPropertyPlaceholder}}, so
existing Camel applications work after upgrading blueprint.core to 1.10.0 (new
1.10.1 actually). WDYT?
> Support fixed property placeholders from Aries blueprint
> --------------------------------------------------------
>
> Key: CAMEL-12570
> URL: https://issues.apache.org/jira/browse/CAMEL-12570
> Project: Camel
> Issue Type: Bug
> Components: camel-blueprint
> Affects Versions: 2.21.1
> Reporter: Grzegorz Grzybek
> Assignee: Grzegorz Grzybek
> Priority: Major
> Fix For: 2.21.2, 2.22.0
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
