You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Martin Gilday (JIRA)" <ji...@apache.org> on 2008/11/10 11:20:05 UTC
[jira] Created: (CAMEL-1066) Property replacement has no effect
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
Priority: Critical
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.
[jira] Commented: (CAMEL-1066) Spring property placesholder has no
effect
Posted by "Martin Gilday (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=47208#action_47208 ]
Martin Gilday commented on CAMEL-1066:
--------------------------------------
I think it is this issue http://jira.springframework.org/browse/SPR-4466
> 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.
[jira] Commented: (CAMEL-1066) Spring property placesholder has no
effect
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=47420#action_47420 ]
Claus Ibsen commented on CAMEL-1066:
------------------------------------
Updated FAQ with the entry to the SPR issue.
> 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
> Fix For: Future
>
>
> 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.
[jira] Updated: (CAMEL-1066) Property replacement has no effect
Posted by "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.
[jira] Resolved: (CAMEL-1066) Spring property placesholder to be
fully supported
Posted by "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 resolved CAMEL-1066.
--------------------------------
Resolution: Won't Fix
Fix Version/s: (was: Future)
We have the Camel properties component which supports property placeholders fully.
Using Spring property placeholders is not possible unless Spring Framework makes that possible.
> Spring property placesholder to be fully supported
> --------------------------------------------------
>
> Key: CAMEL-1066
> URL: https://issues.apache.org/activemq/browse/CAMEL-1066
> Project: Apache Camel
> Issue Type: Improvement
> 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.
[jira] Updated: (CAMEL-1066) Spring property placesholder to be
fully supported
Posted by "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:
-------------------------------
Summary: Spring property placesholder to be fully supported (was: Spring property placesholder has no effect)
Issue Type: Improvement (was: Bug)
Fix Version/s: Future
> Spring property placesholder to be fully supported
> --------------------------------------------------
>
> Key: CAMEL-1066
> URL: https://issues.apache.org/activemq/browse/CAMEL-1066
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-spring
> Affects Versions: 1.5.0
> Reporter: Martin Gilday
> Fix For: Future
>
>
> 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.
[jira] Commented: (CAMEL-1066) Property replacement has no effect
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=47205#action_47205 ]
Claus Ibsen commented on CAMEL-1066:
------------------------------------
See FAQ:
http://activemq.apache.org/camel/how-do-i-use-spring-property-placeholder-with-camel-xml.html
> 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
> Priority: Critical
>
> 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.
[jira] Updated: (CAMEL-1066) Spring property placesholder has no
effect
Posted by "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:
-------------------------------
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.