[CAMEL-10038] BlueprintPropertiesParser breaks propertyPlaceholder fallbackToUnaugmentedProperty behavior

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.15.1
• Fix Version/s: 2.17.3, 2.18.0
• Component/s: camel-blueprint
• Labels: patch

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)

• Patch Info: Patch Available
• Estimated Complexity: Novice
• Assignee: Grzegorz Grzybek
• Reporter: Matthew Zipay
• Created: 09/Jun/16 16:13
• Updated: 25/Jul/16 15:27
• Resolved: 21/Jul/16 07:17

Description

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.

Issue Links

• relates to: CAMEL-7630 BlueprintPropertiesParser doesn't handle the Blueprint Encryption: EncryptionOperationNotPossibleException
• links to: GitHub Pull Request #1075