[CAMEL-1066] Spring property placesholder to be fully supported

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 1.5.0
• Component/s: camel-spring
• Assignee: Unassigned
• Reporter: Martin Gilday
• Created: 10/Nov/08 10:19
• Updated: 24/Apr/11 10:00
• Resolved: 17/Feb/10 14:11

Description

When using a Spring PropertyPlaceholderConfigurer, properties are not replaced into the Camel DSL. A use case for using property substitution is to change the component type used in different deployments of the same app (such as between SEDA and JMS). You can then also use the same config file for testing by replacing JMS endpoints with mock ones.

For example:

<camel:camelContext trace="${traceMode}" useJmx="false">
  <camel:route>
    <camel:from uri="${queue.incoming}" />
    <camel:to uri="${queue.outgoing}" />
  </camel:route>
</camel:camelContext>

In Camel 1.5 the resulting routes are still named ${queue.incoming} instead of being replaced with jms:myQueue etc.

Issue Links

• duplicates: CAMEL-674 Spring property placeholders fully supported