camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthew Zipay (JIRA)" <>
Subject [jira] [Commented] (CAMEL-10038) BlueprintPropertiesParser breaks propertyPlaceholder fallbackToUnaugmentedProperty behavior
Date Wed, 20 Jul 2016 16:02:20 GMT


Matthew Zipay commented on CAMEL-10038:

[~davsclaus] and [~gzres], the pull request now includes a unit test for the fallbackToUnaugmentedProperty
relative to BlueprintPropertiesParser.

Both org.apache.camel.test.blueprint.ConfigAdminNoDefaultValuesBlueprintCreationTest and the
new org.apache.camel.test.blueprint.BlueprintAugmentedPropertiesFallbackTest test cases are
now passing on 2.18-SNAPSHOT.

> BlueprintPropertiesParser breaks propertyPlaceholder fallbackToUnaugmentedProperty behavior
> -------------------------------------------------------------------------------------------
>                 Key: CAMEL-10038
>                 URL:
>             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
>            Reporter: Matthew Zipay
>            Assignee: Grzegorz Grzybek
>            Priority: Minor
>              Labels: patch
>         Attachments: CAMEL-10038.patch, 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

View raw message