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 2010/09/28 14:34:40 UTC

[jira] Created: (CAMEL-3171) Allow property placeholders to be used anywhere in Spring XML (and blueprint as well)

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.


[jira] Commented: (CAMEL-3171) Allow property placeholders to be used anywhere in Spring XML (and blueprint as well)

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/CAMEL-3171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62365#action_62365 ] 

Claus Ibsen commented on CAMEL-3171:
------------------------------------

We could have special type converter which converts from String -> String and detects any property placeholders and does the lookup.

This allows you to use the properties placeholders in any xs:string type in the XSD.

> 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.


[jira] Commented: (CAMEL-3171) Allow property placeholders to be used anywhere in Spring XML (and blueprint as well)

Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
    [ 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.


[jira] Commented: (CAMEL-3171) Allow property placeholders to be used anywhere in Spring XML (and blueprint as well)

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
    [ 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.


[jira] Commented: (CAMEL-3171) Allow property placeholders to be used anywhere in Spring XML (and blueprint as well)

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/CAMEL-3171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62194#action_62194 ] 

Claus Ibsen commented on CAMEL-3171:
------------------------------------

Defining the routes in the <routeContext> tag allow us to be in control. Where as inside the <camelContext> we are in the mercy of Spring namespace handler which has some serious limitations in terms of property placeholders resolution.


> 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.