[
https://issues.apache.org/activemq/browse/CAMEL-3171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62368#action_62368
]
Guillaume Nodet commented on CAMEL-3171:
----------------------------------------
Not sure to understand the issue. Is the issue in the xsd (which defines for
example xsd:int, so can't be validated) or in the namespace handler?
The only way to fix the xsd would be to relax the schema generation and use
strings somehow (i guess there are jaxb2 annotation to enforce the xsd:type to
use).
Not sure what the problem / limitations with placeholders you're talking about
are.
> 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.