Do you define the propertyPlaceholder component anywhere in your context? http://camel.apache.org/using-propertyplaceholder.html
On Mon, Sep 9, 2013 at 1:47 PM, bonnahu <bonn...@gmail.com> wrote: > Running on Camel 2.11.1. > I am trying to use a defined VM argument (e.g., -Dprop.env=DEV) in camel > context. > However, I got the error saying "PropertiesComponent with name properties > must be defined in CamelContext to support property placeholders". So I > need to add a propertyPlaceholder to make it > work. I guess it is related to this issue > > https://issues.apache.org/jira/browse/CAMEL-6313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel > > But according to the comment, this issue has been fixed in 2.11.1. Did I > make any mistake here? > > > > <camel:camelContext xmlns="http://camel.apache.org/schema/spring"; > > > <camel:route> > <camel:from uri="file:src/data?noop=true"/> > <camel:choice> > <camel:when> > <camel:xpath>/person/city = 'London'</camel:xpath> > > <camel:log message="<b>{{prop.env}}*"/> > <camel:to uri="file:target/messages/uk"/> > </camel:when> > <camel:otherwise> > <camel:log message="Other message"/> > <camel:to uri="file:target/messages/others"/> > </camel:otherwise> > </camel:choice> > </camel:route> > </camel:camelContext> > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Got-an-error-PropertiesComponent-with-name-properties-must-be-defined-in-CamelContext-to-support-pro-tp5738974.html > Sent from the Camel - Users mailing list archive at Nabble.com. > -- *Christian Posta* http://www.christianposta.com/blog twitter: @christianposta
