[
https://issues.apache.org/jira/browse/CAMEL-7821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14133907#comment-14133907
]
Martin Kühl commented on CAMEL-7821:
------------------------------------
Reproduction repository at
https://github.com/ewerk/bug-report_camel-bridge-property-placeholder-parser
Run {{gradle test}} to reproduce, switch to branch "split" to see the
workaround of using distinct property placeholders for Spring and Camel.
> BridgePropertyPlaceholderConfigurer fails to use custom PropertiesParser
> ------------------------------------------------------------------------
>
> Key: CAMEL-7821
> URL: https://issues.apache.org/jira/browse/CAMEL-7821
> Project: Camel
> Issue Type: Bug
> Components: camel-spring
> Affects Versions: 2.13.2
> Reporter: Martin Kühl
> Priority: Minor
>
> A {{BridgePropertyPlaceholderConfigurer}} configured to use a custom
> {{PropertiesParser}} like this:
> {code:}
> <bean id="bridgePropertyPlaceholder"
> class="org.apache.camel.spring.spi.BridgePropertyPlaceholderConfigurer"
> p:location="classpath:application.properties"
> p:parser-ref="jasyptParser" />
> {code}
> fails to actually use the parser to parse properties.
> It seems that
> {{org.apache.camel.spring.CamelContextFactoryBean#initPropertyPlaceholder}},
> which is called from {{afterPropertiesSet}}, overwrites the custom parser
> with the default parser from the properties component (on line 279).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
