[jira] Updated: (CAMEL-1066) Property replacement has no effect

["Claus Ibsen (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/activemq/browse/CAMEL-1066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen updated CAMEL-1066:
-------------------------------

    Priority: Major  (was: Critical)

Lowering priority - cant be critical.

Requires Spring 3.0 as spring has to do some internal changes to allow custom spring handlers to get access to the property place holder stuff. There should be a JIRA ticket in the spring roadmap filed by James Strachan about this.

> Property replacement has no effect
> ----------------------------------
>
>                 Key: CAMEL-1066
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-1066
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: camel-spring
>    Affects Versions: 1.5.0
>            Reporter: Martin Gilday
>
> 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:
> {code}
> <camel:camelContext trace="${traceMode}" useJmx="false">
>   <camel:route>
>     <camel:from uri="${queue.incoming}" />
>     <camel:to uri="${queue.outgoing}" />
>   </camel:route>
> </camel:camelContext>
> {code}
> In Camel 1.5 the resulting routes are still named ${queue.incoming} instead of being replaced  with jms:myQueue etc.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.