[
https://issues.apache.org/activemq/browse/CAMEL-3171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62370#action_62370
]
Claus Ibsen commented on CAMEL-3171:
------------------------------------
Yeah its primary the XSD. Because it will spit our xs:int, xs:boolean etc.
The 2nd objective (we should maybe create a new ticket for that) is to let
Camel be able to support property placeholders in any attribute in the XSD.
For example <convertBodyTo charset="{{myCoolCharset}}"/> is not possible today.
To support this we need to do this custom on the EIP pattern. Instead it would
be nice with a more generic solution.
> Allow property placeholders to be used anywhere in Spring XML (and blueprint
> as well)
> -------------------------------------------------------------------------------------
>
> Key: CAMEL-3171
> URL: https://issues.apache.org/activemq/browse/CAMEL-3171
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-blueprint, camel-core, camel-spring
> Affects Versions: 2.4.0
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 3.0.0
>
>
> When using Spring XML or blueprint there is a XSD defining what types the EIP
> attributes uses.
> For example a timeout would be xs:int, and there could be xs:boolean etc.
> But you may want to use property placeholders so you can do
> {code}
> timeout="{{foo.myTimeout}}"
> {code}
> Where {{foo.myTimeout}} is the properties stuff.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
