camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Müller (JIRA) <j...@apache.org>
Subject [jira] [Updated] (CAMEL-5491) Cannot access blueprint property placeholder values from velocity
Date Wed, 08 Aug 2012 22:11:20 GMT

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

Christian Müller updated CAMEL-5491:
------------------------------------

    Affects Version/s: 2.10.0
           Issue Type: Improvement  (was: Bug)

What's your use case?

I assume the properties are fix. Why do you not inject them into a bean/processor which can
set these properties as message headers or exchange properties?
                
> Cannot access blueprint property placeholder values from velocity
> -----------------------------------------------------------------
>
>                 Key: CAMEL-5491
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5491
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-blueprint, camel-velocity
>    Affects Versions: 2.10.0
>            Reporter: Alan Foster
>            Priority: Minor
>
> There isn't a way within velocity to access properties set within the blueprint property-placeholder.
> Currently you can only access the exchange's properties according to the documentation
at http://camel.apache.org/velocity.html

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

Mime
View raw message