Also, if I have a property whose value contains ${ (which I want to be
evaluated by a template engine), I get the same error when referring
to that property (via simple language ==> properties:). The workaround to
this problem isn't as easy as using $simple. I need camel to stop
processing ${ as property placeholders as it did before 2.16.0Thank you, cg On Wednesday, October 14, 2015, Camel Guy <[email protected]> wrote: > Hello, > > I require property placeholders inside and outside of <camelContext> (see > https://issues.apache.org/jira/browse/CAMEL-7849). > > I have the following defined outside <camelContext>: > > <bean id="jasypt" > class="org.apache.camel.component.jasypt.JasyptPropertiesParser"> > <property name="password" value="sysenv:PROPERTIES_KEY"/> > </bean> > <bean id="bridgePropertyPlaceholder" class= > "org.apache.camel.spring.spi.BridgePropertyPlaceholderConfigurer"> > <property name="locations" > > <list> > <value>classpath:default.properties</value> > </list></property> > <property name='parser' ref='jasypt'/> > </bean> > > Unlike in 2.15.3, <log message="${body}"> throws errors like: > > Could not resolve placeholder 'body' in string value "${body}" > > It appears that the {{ }} alternative syntax is not getting engaged inside > <camelContext>. > > I must instead use $simple{body}. This occurs throughout the camelContext > (e.g., inside <filter><simple> > > I tried adding, to no avail, : > > <propertyPlaceholder id="properties" propertiesParserRef="jasypt" > location='classpath:foo.properties'/> > > <simple>$simple{}</simple> doesn't look great. > > I'm wondering why others haven't found this in 2.16.0. I searched the > mailing list and the interwebtubes and couldn't find anything. > > > Thank you, > ~cg >
