[
https://issues.apache.org/jira/browse/CAMEL-10038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15331924#comment-15331924
]
Matthew Zipay commented on CAMEL-10038:
---------------------------------------
Disregard the patch - it will not work. After looking into this further, and
trying a number of workarounds, it is apparent that BlueprintPropertiesParser
is simply not capable of handling augmented properties properly. The choice
appears to be either (a) use Blueprint property placeholder and not augmented
properties or (b) use augmented properties and not Blueprint property
placeholder. Unfortunately this is a significant blocker for me.
I am still trying other workarounds, but at the very least the Camel
documentation should be updated as it is very misleading. The documentation for
fallbackToUnaugmentedProperty makes no mention of this behavior being
impossible with a bridged Blueprint property placeholder, nor does
camel-blueprint javadoc.
> BlueprintPropertiesParser breaks propertyPlaceholder
> fallbackToUnaugmentedProperty behavior
> -------------------------------------------------------------------------------------------
>
> Key: CAMEL-10038
> URL: https://issues.apache.org/jira/browse/CAMEL-10038
> Project: Camel
> Issue Type: Bug
> Components: camel-blueprint
> Affects Versions: 2.15.1
> Environment: Camel 2.15.1.redhat-620133
> JBoss Fuse 6.2.0.redhat-133
> openjdk version "1.8.0_45"
> OpenJDK Runtime Environment (build 1.8.0_45-b13)
> OpenJDK 64-Bit Server VM (build 25.45-b02, mixed mode)
> Linux 3.10.0-229.1.2.el7.x86_64 #1 SMP Fri Mar 6 17:12:08 EST 2015 x86_64
> GNU/Linux (RHEL 7)
> Reporter: Matthew Zipay
> Assignee: Grzegorz Grzybek
> Priority: Minor
> Labels: patch
> Attachments: camel-context.xml, example.bpp.fallback.cfg
>
>
> When BlueprintPropertiesParser parses an "augmented" property key that is not
> found (i.e. value is null), it does not return the null value so that the
> fallbackToUnaugmentedProperty="true" (default) behavior can run. Instead, it
> immediately throws an IllegalArgumentException.
> As a result, it appears to be impossible to take advantage of
> fallbackToUnaugmentedProperty="true" behavior when using the Blueprint
> properties resolver/parser.
> I discovered this against Red Hat's JBoss Fuse impl of Camel, but am
> reporting it here because it appears to be a bug in base Camel. More details
> in comments.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
