You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2008/11/10 11:36:05 UTC

[jira] Updated: (CAMEL-1066) Spring property placesholder has no effect

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

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

    Summary: Spring property placesholder has no effect  (was: Property replacement has no effect)

I also think we have a ticket for this request in our tracker somewhere. 

> Spring property placesholder 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.