camel-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (Confluence)" <conflue...@apache.org>
Subject [CONF] Apache Camel > Using PropertyPlaceholder
Date Mon, 26 Aug 2013 11:38:00 GMT
<html>
<head>
    <base href="https://cwiki.apache.org/confluence">
            <link rel="stylesheet" href="/confluence/s/en/2176/1/1/_/styles/combined.css?spaceKey=CAMEL&amp;forWysiwyg=true" type="text/css">
    </head>
<body style="background: white;" bgcolor="white" class="email-body">
<div id="pageContent">
<div id="notificationFormat">
<div class="wiki-content">
<div class="email">
    <h2><a href="https://cwiki.apache.org/confluence/display/CAMEL/Using+PropertyPlaceholder">Using PropertyPlaceholder</a></h2>
    <h4>Page <b>edited</b> by             <a href="https://cwiki.apache.org/confluence/display/~davsclaus">Claus Ibsen</a>
    </h4>
        <br/>
                         <h4>Changes (2)</h4>
                                 
    
<div id="page-diffs">
                    <table class="diff" cellpadding="0" cellspacing="0">
    
            <tr><td class="diff-snipped" >...<br></td></tr>
            <tr><td class="diff-unchanged" >- additional supported in Spring XML (see below in examples) <br>- using Blueprint PropertyPlaceholder with Camel [Properties] component <br></td></tr>
            <tr><td class="diff-added-lines" style="background-color: #dfd;">- using {{@PropertyInject}} to inject a property in a POJO <br></td></tr>
            <tr><td class="diff-unchanged" > <br>h3. Syntax <br></td></tr>
            <tr><td class="diff-snipped" >...<br></td></tr>
            <tr><td class="diff-unchanged" > <br>The {{ignoreMissingLocationWithPropertiesComponent}} can be used to instruct Camel to ignore any locations which was not discoverable, for example if you run the unit test, in an environment that does not have access to the location of the properties.  <br></td></tr>
            <tr><td class="diff-added-lines" style="background-color: #dfd;"> <br> <br>h3. Using @PropertyInject <br>*Available as of Camel 2.12* <br> <br>Camel allows to inject property placeholders in POJOs using the @PropertyInject annotation which can be set on fields and setter methods. <br>For example you can use that with {{RouteBuilder}} classes, such as shown below: <br> <br>{code:java} <br>public class MyRouteBuilder extends RouteBuilder { <br> <br>    @PropertyInject(&quot;hello&quot;) <br>    private String greeting; <br> <br>    @Override <br>    public void configure() throws Exception { <br>        from(&quot;direct:start&quot;) <br>            .transform().constant(greeting) <br>            .to(&quot;{{result}}&quot;); <br>    } <br> <br>} <br>{code} <br> <br>Notice we have annotated the greeting field with @PropertyInject and define it to use the key &quot;hello&quot;. Camel will then lookup the property with this key and inject its value, converted to a String type. <br> <br>You can also use multiple placeholders and text in the key, for example we can do: <br>{code} <br>    @PropertyInject(&quot;Hello {{name}} how are you?&quot;) <br>    private String greeting; <br>{code} <br> <br>This will lookup the placeholder with they key &quot;name&quot;. <br> <br>You can also add a default value if the key does not exists, such as: <br>{code} <br>    @PropertyInject(&quot;myTimeout&quot;, default = &quot;5000&quot;) <br>    private int timeout; <br>{code} <br></td></tr>
    
            </table>
    </div>                            <h4>Full Content</h4>
                    <div class="notificationGreySide">
        <h2><a name="UsingPropertyPlaceholder-UsingPropertyPlaceholder"></a>Using PropertyPlaceholder</h2>
<p><b>Available as of Camel 2.3</b></p>

<p>Camel now provides a new <tt>PropertiesComponent</tt> in <b>camel-core</b> which allows you to use property placeholders when defining Camel <a href="/confluence/display/CAMEL/Endpoint" title="Endpoint">Endpoint</a> URIs. <br/>
This works much like you would do if using Spring's <tt>&lt;property-placeholder&gt;</tt> tag. However Spring have a limitation which prevents 3rd party frameworks to leverage Spring property placeholders to the fullest. See more at <a href="/confluence/display/CAMEL/How+do+I+use+Spring+Property+Placeholder+with+Camel+XML" title="How do I use Spring Property Placeholder with Camel XML">How do I use Spring Property Placeholder with Camel XML</a>.</p>

<div class='panelMacro'><table class='tipMacro'><colgroup><col width='24'><col></colgroup><tr><td valign='top'><img src="/confluence/images/icons/emoticons/check.gif" width="16" height="16" align="absmiddle" alt="" border="0"></td><td><b>Bridging Spring and Camel property placeholders</b><br />From Camel 2.10 onwards, you can bridge the Spring property placeholder with Camel, see further below for more details.</td></tr></table></div>

<p>The property placeholder is generally in use when doing:</p>
<ul class="alternate" type="square">
	<li>lookup or creating endpoints</li>
	<li>lookup of beans in the <a href="/confluence/display/CAMEL/Registry" title="Registry">Registry</a></li>
	<li>additional supported in Spring XML (see below in examples)</li>
	<li>using Blueprint PropertyPlaceholder with Camel <a href="/confluence/display/CAMEL/Properties" title="Properties">Properties</a> component</li>
	<li>using <tt>@PropertyInject</tt> to inject a property in a POJO</li>
</ul>


<h3><a name="UsingPropertyPlaceholder-Syntax"></a>Syntax</h3>
<p>The syntax to use Camel's property placeholder is to use {{<tt>key</tt>}} for example {{<tt>file.uri</tt>}} where <tt>file.uri</tt> is the property key.<br/>
You can use property placeholders in parts of the endpoint URI's which for example you can use placeholders for parameters in the URIs.</p>

<h3><a name="UsingPropertyPlaceholder-PropertyResolver"></a>PropertyResolver</h3>
<p>Camel provides a pluggable mechanism which allows 3rd part to provide their own resolver to lookup properties. Camel provides a default implementation <tt>org.apache.camel.component.properties.DefaultPropertiesResolver</tt> which is capable of loading properties from the file system, classpath or <a href="/confluence/display/CAMEL/Registry" title="Registry">Registry</a>. You can prefix the locations with either:</p>
<ul class="alternate" type="square">
	<li><tt>ref:</tt> <b>Camel 2.4:</b> to lookup in the <a href="/confluence/display/CAMEL/Registry" title="Registry">Registry</a></li>
	<li><tt>file:</tt> to load the from file system</li>
	<li><tt>classpath:</tt> to load from classpath (this is also the default if no prefix is provided)</li>
	<li><tt>blueprint:</tt> <b>Camel 2.7:</b> to use a specific OSGi blueprint placeholder service</li>
</ul>


<h3><a name="UsingPropertyPlaceholder-Defininglocation"></a>Defining location</h3>
<p>The <tt>PropertiesResolver</tt> need to know a location(s) where to resolve the properties. You can define 1 to many locations. If you define the location in a single String property you can separate multiple locations with comma such as:</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
<pre class="theme: Default; brush: java; gutter: false" style="font-size:12px; font-family: ConfluenceInstalledFont,monospace;">
pc.setLocation("com/mycompany/myprop.properties,com/mycompany/other.properties");
</pre>
</div></div>

<h4><a name="UsingPropertyPlaceholder-Usingsystemandenvironmentvariablesinlocations"></a>Using system and environment variables in locations</h4>
<p><b>Available as of Camel 2.7</b></p>

<p>The location now supports using placeholders for JVM system properties and OS environments variables.</p>

<p>For example:</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
<pre class="theme: Default; brush: java; gutter: false" style="font-size:12px; font-family: ConfluenceInstalledFont,monospace;">
location=file:${karaf.home}/etc/foo.properties
</pre>
</div></div>

<p>In the location above we defined a location using the file scheme using the JVM system property with key <tt>karaf.home</tt>.</p>

<p>To use an OS environment variable instead you would have to prefix with env:</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
<pre class="theme: Default; brush: java; gutter: false" style="font-size:12px; font-family: ConfluenceInstalledFont,monospace;">
location=file:${env:APP_HOME}/etc/foo.properties
</pre>
</div></div>
<p>Where <tt>APP_HOME</tt> is an OS environment.</p>

<p>You can have multiple placeholders in the same location, such as:</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
<pre class="theme: Default; brush: java; gutter: false" style="font-size:12px; font-family: ConfluenceInstalledFont,monospace;">
location=file:${env:APP_HOME}/etc/${prop.name}.properties
</pre>
</div></div>


<h3><a name="UsingPropertyPlaceholder-ConfiguringinJavaDSL"></a>Configuring in Java DSL</h3>
<p>You have to create and register the <tt>PropertiesComponent</tt> under the name <tt>properties</tt> such as:</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
<pre class="theme: Default; brush: java; gutter: false" style="font-size:12px; font-family: ConfluenceInstalledFont,monospace;">
PropertiesComponent pc = new PropertiesComponent();
pc.setLocation("classpath:com/mycompany/myprop.properties");
context.addComponent("properties", pc);
</pre>
</div></div>

<h3><a name="UsingPropertyPlaceholder-ConfiguringinSpringXML"></a>Configuring in Spring XML</h3>
<p>Spring XML offers two variations to configure. You can define a spring bean as a <tt>PropertiesComponent</tt> which resembles the way done in Java DSL. Or you can use the <tt>&lt;propertyPlaceholder&gt;</tt> tag.</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
<pre class="theme: Default; brush: xml; gutter: false" style="font-size:12px; font-family: ConfluenceInstalledFont,monospace;">
&lt;bean id="properties" class="org.apache.camel.component.properties.PropertiesComponent"&gt;
    &lt;property name="location" value="classpath:com/mycompany/myprop.properties"/&gt;
&lt;/bean&gt;
</pre>
</div></div>

<p>Using the <tt>&lt;propertyPlaceholder&gt;</tt> tag makes the configuration a bit more fresh such as:</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
<pre class="theme: Default; brush: xml; gutter: false" style="font-size:12px; font-family: ConfluenceInstalledFont,monospace;">
&lt;camelContext ...&gt;
   &lt;propertyPlaceholder id="properties" location="com/mycompany/myprop.properties"/&gt;
&lt;/camelContext&gt;
</pre>
</div></div>

<div class='panelMacro'><table class='tipMacro'><colgroup><col width='24'><col></colgroup><tr><td valign='top'><img src="/confluence/images/icons/emoticons/check.gif" width="16" height="16" align="absmiddle" alt="" border="0"></td><td><b>Specifying the cache option inside XML</b><br />Camel 2.10 onwards supports specifying a value for the cache option both inside the Spring as well as the Blueprint XML.</td></tr></table></div>

<h3><a name="UsingPropertyPlaceholder-UsingaPropertiesfromtheRegistry"></a>Using a Properties from the <a href="/confluence/display/CAMEL/Registry" title="Registry">Registry</a></h3>
<p><b>Available as of Camel 2.4</b><br/>
For example in OSGi you may want to expose a service which returns the properties as a <tt>java.util.Properties</tt> object.</p>

<p>Then you could setup the <a href="/confluence/display/CAMEL/Properties" title="Properties">Properties</a> component as follows:</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
<pre class="theme: Default; brush: xml; gutter: false" style="font-size:12px; font-family: ConfluenceInstalledFont,monospace;">
   &lt;propertyPlaceholder id="properties" location="ref:myProperties"/&gt;
</pre>
</div></div>
<p>Where <tt>myProperties</tt> is the id to use for lookup in the OSGi registry. Notice we use the <tt>ref:</tt> prefix to tell Camel that it should lookup the properties for the <a href="/confluence/display/CAMEL/Registry" title="Registry">Registry</a>.</p>

<h3><a name="UsingPropertyPlaceholder-Examplesusingpropertiescomponent"></a>Examples using properties component</h3>
<p>When using property placeholders in the endpoint URIs you can either use the <tt>properties:</tt> component or define the placeholders directly in the URI. We will show example of both cases, starting with the former.</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
<pre class="theme: Default; brush: java; gutter: false" style="font-size:12px; font-family: ConfluenceInstalledFont,monospace;">
// properties
cool.end=mock:result

// route
from("direct:start").to("properties:{{cool.end}}");
</pre>
</div></div>

<p>You can also use placeholders as a part of the endpoint uri:</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
<pre class="theme: Default; brush: java; gutter: false" style="font-size:12px; font-family: ConfluenceInstalledFont,monospace;">
// properties
cool.foo=result

// route
from("direct:start").to("properties:mock:{{cool.foo}}");
</pre>
</div></div>
<p>In the example above the to endpoint will be resolved to <tt>mock:result</tt>.</p>

<p>You can also have properties with refer to each other such as:</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
<pre class="theme: Default; brush: java; gutter: false" style="font-size:12px; font-family: ConfluenceInstalledFont,monospace;">
// properties
cool.foo=result
cool.concat=mock:{{cool.foo}}

// route
from("direct:start").to("properties:mock:{{cool.concat}}");
</pre>
</div></div>
<p>Notice how <tt>cool.concat</tt> refer to another property.</p>

<p>The <tt>properties:</tt> component also offers you to override and provide a location in the given uri using the <tt>locations</tt> option:</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
<pre class="theme: Default; brush: java; gutter: false" style="font-size:12px; font-family: ConfluenceInstalledFont,monospace;">
   from("direct:start").to("properties:bar.end?locations=com/mycompany/bar.properties");
</pre>
</div></div>

<h3><a name="UsingPropertyPlaceholder-Examples"></a>Examples</h3>
<p>You can also use property placeholders directly in the endpoint uris without having to use <tt>properties:</tt>.</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
<pre class="theme: Default; brush: java; gutter: false" style="font-size:12px; font-family: ConfluenceInstalledFont,monospace;">
// properties
cool.foo=result

// route
from("direct:start").to("mock:{{cool.foo}}");
</pre>
</div></div>

<p>And you can use them in multiple wherever you want them:</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
<pre class="theme: Default; brush: java; gutter: false" style="font-size:12px; font-family: ConfluenceInstalledFont,monospace;">
// properties
cool.start=direct:start
cool.showid=true
cool.result=result

// route
from("{{cool.start}}")
    .to("log:{{cool.start}}?showBodyType=false&amp;showExchangeId={{cool.showid}}")
    .to("mock:{{cool.result}}");
</pre>
</div></div>

<p>You can also your property placeholders when using <a href="/confluence/display/CAMEL/ProducerTemplate" title="ProducerTemplate">ProducerTemplate</a> for example:</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
<pre class="theme: Default; brush: java; gutter: false" style="font-size:12px; font-family: ConfluenceInstalledFont,monospace;">
template.sendBody("{{cool.start}}", "Hello World");
</pre>
</div></div>

<h3><a name="UsingPropertyPlaceholder-ExamplewithSimplelanguage"></a>Example with <a href="/confluence/display/CAMEL/Simple" title="Simple">Simple</a> language</h3>
<p>The <a href="/confluence/display/CAMEL/Simple" title="Simple">Simple</a> language now also support using property placeholders, for example in the route below:</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
<pre class="theme: Default; brush: java; gutter: false" style="font-size:12px; font-family: ConfluenceInstalledFont,monospace;">
// properties
cheese.quote=Camel rocks

// route
from("direct:start")
    .transform().simple("Hi ${body} do you think ${properties:cheese.quote}?");
</pre>
</div></div>

<p>You can also specify the location in the <a href="/confluence/display/CAMEL/Simple" title="Simple">Simple</a> language for example:</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
<pre class="theme: Default; brush: java; gutter: false" style="font-size:12px; font-family: ConfluenceInstalledFont,monospace;">
// bar.properties
bar.quote=Beer tastes good

// route
from("direct:start")
    .transform().simple("Hi ${body}. ${properties:com/mycompany/bar.properties:bar.quote}.");
</pre>
</div></div>


<h3><a name="UsingPropertyPlaceholder-AdditionalpropertyplaceholdersupportedinSpringXML"></a>Additional property placeholder supported in Spring XML</h3>
<p>The property placeholders is also supported in many of the Camel Spring XML tags such as <tt>&lt;package&gt;, &lt;packageScan&gt;, &lt;contextScan&gt;, &lt;jmxAgent&gt;, &lt;endpoint&gt;, &lt;routeBuilder&gt;, &lt;proxy&gt;</tt> and the others.</p>

<p>The example below has property placeholder in the &lt;jmxAgent&gt; tag:</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
<script type="syntaxhighlighter" class="theme: Default; brush: xml; gutter: false"><![CDATA[
&lt;camelContext xmlns="http://camel.apache.org/schema/spring"&gt;
    &lt;propertyPlaceholder id="properties" location="org/apache/camel/spring/jmx.properties"/&gt;

    &lt;!-- we can use propery placeholders when we define the JMX agent --&gt;
    &lt;jmxAgent id="agent" registryPort="{{myjmx.port}}" disabled="{{myjmx.disabled}}"
              usePlatformMBeanServer="{{myjmx.usePlatform}}"
              createConnector="true"
              statisticsLevel="RoutesOnly"/&gt;

    &lt;route id="foo" autoStartup="false"&gt;
        &lt;from uri="seda:start"/&gt;
        &lt;to uri="mock:result"/&gt;
    &lt;/route&gt;

&lt;/camelContext&gt;
]]></script>
</div></div>

<p>You can also define property placeholders in the various attributes on the &lt;camelContext&gt; tag such as <tt>trace</tt> as shown here:</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
<script type="syntaxhighlighter" class="theme: Default; brush: xml; gutter: false"><![CDATA[
&lt;camelContext trace="{{foo.trace}}" xmlns="http://camel.apache.org/schema/spring"&gt;
    &lt;propertyPlaceholder id="properties" location="org/apache/camel/spring/processor/myprop.properties"/&gt;

    &lt;template id="camelTemplate" defaultEndpoint="{{foo.cool}}"/&gt;

    &lt;route&gt;
        &lt;from uri="direct:start"/&gt;
        &lt;setHeader headerName="{{foo.header}}"&gt;
            &lt;simple&gt;${in.body} World!&lt;/simple&gt;
        &lt;/setHeader&gt;
        &lt;to uri="mock:result"/&gt;
    &lt;/route&gt;
&lt;/camelContext&gt;
]]></script>
</div></div>

<h3><a name="UsingPropertyPlaceholder-OverridingapropertysettingusingaJVMSystemProperty"></a>Overriding a property setting using a JVM System Property</h3>
<p><b>Available as of Camel 2.5</b><br/>
It is possible to override a property value at runtime using a JVM System property without the need to restart the application to pick up the change. This may also be accomplished from the command line by creating a JVM System property of the same name as the property it replaces with a new value. An example of this is given below</p>

<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
<pre class="theme: Default; brush: java; gutter: false" style="font-size:12px; font-family: ConfluenceInstalledFont,monospace;">
PropertiesComponent pc = context.getComponent("properties", PropertiesComponent.class);
pc.setCache(false);
        
System.setProperty("cool.end", "mock:override");
System.setProperty("cool.result", "override");

context.addRoutes(new RouteBuilder() {
    @Override
    public void configure() throws Exception {
        from("direct:start").to("properties:cool.end");
        from("direct:foo").to("properties:mock:{{cool.result}}");
    }
});
context.start();

getMockEndpoint("mock:override").expectedMessageCount(2);

template.sendBody("direct:start", "Hello World");
template.sendBody("direct:foo", "Hello Foo");

System.clearProperty("cool.end");
System.clearProperty("cool.result");
        
assertMockEndpointsSatisfied();
</pre>
</div></div>  

<h3><a name="UsingPropertyPlaceholder-UsingpropertyplaceholdersforanykindofattributeintheXMLDSL"></a>Using property placeholders for any kind of attribute in the XML DSL</h3>
<p><b>Available as of Camel 2.7</b></p>

<div class='panelMacro'><table class='infoMacro'><colgroup><col width='24'><col></colgroup><tr><td valign='top'><img src="/confluence/images/icons/emoticons/information.gif" width="16" height="16" align="absmiddle" alt="" border="0"></td><td>If you use OSGi Blueprint then this only works from <b>2.11.1</b> or <b>2.10.5</b> onwards.</td></tr></table></div>

<p>Previously it was only the <tt>xs:string</tt> type attributes in the XML DSL that support placeholders. For example often a timeout attribute would be a <tt>xs:int</tt> type and thus you cannot set a string value as the placeholder key. This is now possible from Camel 2.7 onwards using a special placeholder namespace.</p>

<p>In the example below we use the <tt>prop</tt> prefix for the namespace <tt><a href="http://camel.apache.org/schema/placeholder" class="external-link" rel="nofollow">http://camel.apache.org/schema/placeholder</a></tt> by which we can use the <tt>prop</tt> prefix in the attributes in the XML DSLs. Notice how we use that in the <a href="/confluence/display/CAMEL/Multicast" title="Multicast">Multicast</a> to indicate that the option <tt>stopOnException</tt> should be the value of the placeholder with the key "stop".</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
<script type="syntaxhighlighter" class="theme: Default; brush: xml; gutter: false"><![CDATA[
&lt;beans xmlns="http://www.springframework.org/schema/beans"
       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       xmlns:prop="http://camel.apache.org/schema/placeholder"
       xsi:schemaLocation="
       http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd
       http://camel.apache.org/schema/spring http://camel.apache.org/schema/spring/camel-spring.xsd
    "&gt;

    &lt;!-- Notice in the declaration above, we have defined the prop prefix as the Camel placeholder namespace --&gt;

    &lt;bean id="damn" class="java.lang.IllegalArgumentException"&gt;
        &lt;constructor-arg index="0" value="Damn"/&gt;
    &lt;/bean&gt;

    &lt;camelContext xmlns="http://camel.apache.org/schema/spring"&gt;

        &lt;propertyPlaceholder id="properties"
                             location="classpath:org/apache/camel/component/properties/myprop.properties"
                             xmlns="http://camel.apache.org/schema/spring"/&gt;

        &lt;route&gt;
            &lt;from uri="direct:start"/&gt;
            &lt;!-- use prop namespace, to define a property placeholder, which maps to
                 option stopOnException={{stop}} --&gt;
            &lt;multicast prop:stopOnException="stop"&gt;
                &lt;to uri="mock:a"/&gt;
                &lt;throwException ref="damn"/&gt;
                &lt;to uri="mock:b"/&gt;
            &lt;/multicast&gt;
        &lt;/route&gt;

    &lt;/camelContext&gt;

&lt;/beans&gt;
]]></script>
</div></div>

<p>In our properties file we have the value defined as</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
<pre class="theme: Default; brush: java; gutter: false" style="font-size:12px; font-family: ConfluenceInstalledFont,monospace;">
stop=true
</pre>
</div></div>

<h3><a name="UsingPropertyPlaceholder-UsingpropertyplaceholderintheJavaDSL"></a>Using property placeholder in the Java DSL</h3>
<p><b>Available as of Camel 2.7</b></p>

<p>Likewise we have added support for defining placeholders in the Java DSL using the new <tt>placeholder</tt> DSL as shown in the following equivalent example:</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
<script type="syntaxhighlighter" class="theme: Default; brush: java; gutter: false"><![CDATA[
from("direct:start")
    // use a property placeholder for the option stopOnException on the Multicast EIP
    // which should have the value of {{stop}} key being looked up in the properties file
    .multicast().placeholder("stopOnException", "stop")
        .to("mock:a").throwException(new IllegalAccessException("Damn")).to("mock:b");
]]></script>
</div></div>


<h3><a name="UsingPropertyPlaceholder-UsingBlueprintpropertyplaceholderwithCamelroutes"></a>Using Blueprint property placeholder with Camel routes</h3>
<p><b>Available as of Camel 2.7</b></p>

<p>Camel supports <a href="/confluence/display/CAMEL/Using+OSGi+blueprint+with+Camel" title="Using OSGi blueprint with Camel">Blueprint</a> which also offers a property placeholder service. Camel supports convention over configuration, so all you have to do is to define the OSGi Blueprint property placeholder in the XML file as shown below:</p>
<div class="code panel" style="border-width: 1px;"><div class="codeHeader panelHeader" style="border-bottom-width: 1px;"><b>Using OSGi blueprint property placeholders in Camel routes</b></div><div class="codeContent panelContent">
<script type="syntaxhighlighter" class="theme: Default; brush: xml; gutter: false"><![CDATA[
&lt;blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0"
           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
           xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.0.0"
           xsi:schemaLocation="
           http://www.osgi.org/xmlns/blueprint/v1.0.0 http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd"&gt;

    &lt;!-- OSGI blueprint property placeholder --&gt;
    &lt;cm:property-placeholder id="myblueprint.placeholder" persistent-id="camel.blueprint"&gt;
        &lt;!-- list some properties for this test --&gt;
        &lt;cm:default-properties&gt;
            &lt;cm:property name="result" value="mock:result"/&gt;
        &lt;/cm:default-properties&gt;
    &lt;/cm:property-placeholder&gt;

    &lt;camelContext xmlns="http://camel.apache.org/schema/blueprint"&gt;

        &lt;!-- in the route we can use {{ }} placeholders which will lookup in blueprint
             as Camel will auto detect the OSGi blueprint property placeholder and use it --&gt;
        &lt;route&gt;
            &lt;from uri="direct:start"/&gt;
            &lt;to uri="mock:foo"/&gt;
            &lt;to uri="{{result}}"/&gt;
        &lt;/route&gt;

    &lt;/camelContext&gt;

&lt;/blueprint&gt;
]]></script>
</div></div>

<p>By default Camel detects and uses OSGi blueprint property placeholder service. You can disable this by setting the attribute <tt>useBlueprintPropertyResolver</tt> to false on the <tt>&lt;camelContext&gt;</tt> definition.</p>

<div class='panelMacro'><table class='infoMacro'><colgroup><col width='24'><col></colgroup><tr><td valign='top'><img src="/confluence/images/icons/emoticons/information.gif" width="16" height="16" align="absmiddle" alt="" border="0"></td><td><b>About placeholder syntaxes</b><br />Notice how we can use the Camel syntax for placeholders {{ }} in the Camel route, which will lookup the value from OSGi blueprint.<br/>
The blueprint syntax for placeholders is ${ }. So outside the &lt;camelContext&gt; you must use the ${ } syntax. Where as inside &lt;camelContext&gt; you must use {{ }} syntax.<br/>
OSGi blueprint allows you to configure the syntax, so you can actually align those if you want.</td></tr></table></div>

<p>You can also explicit refer to a specific OSGi blueprint property placeholder by its id. For that you need to use the Camel's &lt;propertyPlaceholder&gt; as shown in the example below:</p>
<div class="code panel" style="border-width: 1px;"><div class="codeHeader panelHeader" style="border-bottom-width: 1px;"><b>Explicit referring to a OSGi blueprint placeholder in Camel</b></div><div class="codeContent panelContent">
<script type="syntaxhighlighter" class="theme: Default; brush: xml; gutter: false"><![CDATA[
&lt;blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0"
           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
           xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.0.0"
           xsi:schemaLocation="
           http://www.osgi.org/xmlns/blueprint/v1.0.0 http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd"&gt;

    &lt;!-- OSGI blueprint property placeholder --&gt;
    &lt;cm:property-placeholder id="myblueprint.placeholder" persistent-id="camel.blueprint"&gt;
        &lt;!-- list some properties for this test --&gt;
        &lt;cm:default-properties&gt;
            &lt;cm:property name="prefix.result" value="mock:result"/&gt;
        &lt;/cm:default-properties&gt;
    &lt;/cm:property-placeholder&gt;

    &lt;camelContext xmlns="http://camel.apache.org/schema/blueprint"&gt;

        &lt;!-- using Camel properties component and refer to the blueprint property placeholder by its id --&gt;
        &lt;propertyPlaceholder id="properties" location="blueprint:myblueprint.placeholder"
                             prefixToken="[[" suffixToken="]]"
                             propertyPrefix="prefix."/&gt;

        &lt;!-- in the route we can use {{ }} placeholders which will lookup in blueprint --&gt;
        &lt;route&gt;
            &lt;from uri="direct:start"/&gt;
            &lt;to uri="mock:foo"/&gt;
            &lt;to uri="[[result]]"/&gt;
        &lt;/route&gt;

    &lt;/camelContext&gt;

&lt;/blueprint&gt;
]]></script>
</div></div>

<p>Notice how we use the <tt>blueprint</tt> scheme to refer to the OSGi blueprint placeholder by its id. This allows you to mix and match, for example you can also have additional schemes in the location. For example to load a file from the classpath you can do:</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
<pre class="theme: Default; brush: java; gutter: false" style="font-size:12px; font-family: ConfluenceInstalledFont,monospace;">
location="blueprint:myblueprint.placeholder,classpath:myproperties.properties"
</pre>
</div></div>

<p>Each location is separated by comma.</p>


<h4><a name="UsingPropertyPlaceholder-OverridingBlueprintpropertyplaceholdersoutsideCamelContext"></a>Overriding Blueprint property placeholders outside CamelContext</h4>
<p><b>Available as of Camel 2.10.4</b></p>

<p>When using Blueprint property placeholder in the Blueprint XML file, you can declare the properties directly in the XML file as shown below:</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
<script type="syntaxhighlighter" class="theme: Default; brush: xml; gutter: false"><![CDATA[
&lt;!-- blueprint property placeholders --&gt;
&lt;cm:property-placeholder persistent-id="my-placeholders"&gt;
  &lt;cm:default-properties&gt;
    &lt;cm:property name="greeting" value="Hello"/&gt;
    &lt;cm:property name="destination" value="mock:result"/&gt;
  &lt;/cm:default-properties&gt;
&lt;/cm:property-placeholder&gt;

&lt;!-- a bean that uses a blueprint property placeholder --&gt;
&lt;bean id="myCoolBean" class="org.apache.camel.test.blueprint.MyCoolBean"&gt;
  &lt;property name="say" value="${greeting}"/&gt;
&lt;/bean&gt;

&lt;camelContext xmlns="http://camel.apache.org/schema/blueprint"&gt;

  &lt;route&gt;
    &lt;from uri="direct:start"/&gt;
    &lt;bean ref="myCoolBean" method="saySomething"/&gt;
    &lt;to uri="{{destination}}"/&gt;
  &lt;/route&gt;

&lt;/camelContext&gt;
]]></script>
</div></div>

<p>Notice that we have a &lt;bean&gt; which refers to one of the properties. And in the Camel route we refer to the other using the {{ }} notation.</p>

<p>Now if you want to override these Blueprint properties from an unit test, you can do this as shown below:</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
<script type="syntaxhighlighter" class="theme: Default; brush: java; gutter: false"><![CDATA[
@Override
protected String useOverridePropertiesWithConfigAdmin(Dictionary props) {
    // add the properties we want to override
    props.put("greeting", "Bye");

    // return the PID of the config-admin we are using in the blueprint xml file
    return "my-placeholders";
}
]]></script>
</div></div>

<p>To do this we override and implement the <tt>useOverridePropertiesWithConfigAdmin</tt> method. We can then put the properties we want to override on the given props parameter. And the return value <b>must</b> be the persistence-id of the &lt;cm:property-placeholder&gt; tag, which you define in the blueprint XML file.</p>

<h4><a name="UsingPropertyPlaceholder-Using.cfgor.propertiesfileforBlueprintpropertyplaceholders"></a>Using .cfg or .properties file for Blueprint property placeholders</h4>
<p><b>Available as of Camel 2.10.4</b></p>

<p>When using Blueprint property placeholder in the Blueprint XML file, you can declare the properties in a .properties or .cfg file. If you use Apache ServieMix / Karaf then this container has a convention that it loads the properties from a file in the etc directory with the naming etc/pid.cfg, where pid is the persistence-id.</p>

<p>For example in the blueprint XML file we have the persistence-id="stuff", which mean it will load the configuration file as etc/stuff.cfg.</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
<script type="syntaxhighlighter" class="theme: Default; brush: xml; gutter: false"><![CDATA[
&lt;!-- blueprint property placeholders, that will use etc/stuff.cfg as the properties file --&gt;
&lt;cm:property-placeholder persistent-id="stuff"/&gt;

&lt;!-- a bean that uses a blueprint property placeholder --&gt;
&lt;bean id="myCoolBean" class="org.apache.camel.test.blueprint.MyCoolBean"&gt;
  &lt;property name="say" value="${greeting}"/&gt;
&lt;/bean&gt;

&lt;camelContext xmlns="http://camel.apache.org/schema/blueprint"&gt;

  &lt;route&gt;
    &lt;from uri="direct:start"/&gt;
    &lt;bean ref="myCoolBean" method="saySomething"/&gt;
    &lt;to uri="mock:result"/&gt;
  &lt;/route&gt;

&lt;/camelContext&gt;
]]></script>
</div></div>

<p>Now if you want to unit test this blueprint XML file, then you can override the <tt>loadConfigAdminConfigurationFile</tt> and tell Camel which file to load as shown below:</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
<script type="syntaxhighlighter" class="theme: Default; brush: java; gutter: false"><![CDATA[
@Override
protected String[] loadConfigAdminConfigurationFile() {
    // String[0] = tell Camel the path of the .cfg file to use for OSGi ConfigAdmin in the blueprint XML file
    // String[1] = tell Camel the persistence-id of the cm:property-placeholder in the blueprint XML file
    return new String[]{"src/test/resources/etc/stuff.cfg", "stuff"};
}
]]></script>
</div></div>

<p>Notice that this method requires to return a String[] with 2 values. The 1st value is the path for the configuration file to load.<br/>
The 2nd value is the persistence-id of the &lt;cm:property-placeholder&gt; tag.</p>

<p>The stuff.cfg file is just a plain properties file with the property placeholders such as:</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
<pre class="theme: Default; brush: java; gutter: false" style="font-size:12px; font-family: ConfluenceInstalledFont,monospace;">
## this is a comment
greeting=Bye
</pre>
</div></div>


<h4><a name="UsingPropertyPlaceholder-Using.cfgfileandoverridingpropertiesforBlueprintpropertyplaceholders"></a>Using .cfg file and overriding properties for Blueprint property placeholders</h4>

<p>You can do both as well. Here is a complete example. First we have the Blueprint XML file:</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
<script type="syntaxhighlighter" class="theme: Default; brush: xml; gutter: false"><![CDATA[
&lt;blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0"
           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
           xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.0.0"
           xsi:schemaLocation="
             http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.0.0 http://aries.apache.org/schemas/blueprint-cm/blueprint-cm-1.0.0.xsd
             http://www.osgi.org/xmlns/blueprint/v1.0.0 http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd"&gt;

  &lt;!-- blueprint property placeholders, that will use etc/stuff.cfg as the properties file --&gt;
  &lt;cm:property-placeholder persistent-id="stuff"/&gt;

  &lt;!-- a bean that uses a blueprint property placeholder --&gt;
  &lt;bean id="myCoolBean" class="org.apache.camel.test.blueprint.MyCoolBean"&gt;
    &lt;property name="say" value="${greeting}"/&gt;
    &lt;property name="echo" value="${echo}"/&gt;
  &lt;/bean&gt;

  &lt;camelContext xmlns="http://camel.apache.org/schema/blueprint"&gt;

    &lt;route&gt;
      &lt;from uri="direct:start"/&gt;
      &lt;bean ref="myCoolBean" method="saySomething"/&gt;
      &lt;to uri="{{destination}}"/&gt;
      &lt;bean ref="myCoolBean" method="echoSomething"/&gt;
      &lt;to uri="{{destination}}"/&gt;
    &lt;/route&gt;

  &lt;/camelContext&gt;

&lt;/blueprint&gt;
]]></script>
</div></div>

<p>And in the unit test class we do as follows:</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
<script type="syntaxhighlighter" class="theme: Default; brush: java; gutter: false"><![CDATA[
/**
 * This example will load a Blueprint .cfdg file, and also override its property placeholders from this unit test
 * source code directly.
 */
public class ConfigAdminLoadConfigurationFileAndOverrideTest extends CamelBlueprintTestSupport {

    @Override
    protected String getBlueprintDescriptor() {
        // which blueprint XML file to use for this test
        return "org/apache/camel/test/blueprint/configadmin-loadfileoverride.xml";
    }

    @Override
    protected String[] loadConfigAdminConfigurationFile() {
        // which .cfg file to use, and the name of the persistence-id
        return new String[]{"src/test/resources/etc/stuff.cfg", "stuff"};
    }

    @Override
    protected String useOverridePropertiesWithConfigAdmin(Dictionary props) throws Exception {
        // override / add extra properties
        props.put("destination", "mock:extra");

        // return the persistence-id to use
        return "stuff";
    }

    @Test
    public void testConfigAdmin() throws Exception {
        // regular unit test method
        getMockEndpoint("mock:extra").expectedBodiesReceived("Bye World", "Yay Bye WorldYay Bye World");

        template.sendBody("direct:start", "World");

        assertMockEndpointsSatisfied();
    }

}
]]></script>
</div></div>

<p>And the <tt>etc/stuff.cfg</tt> configuration file contains</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
<pre class="theme: Default; brush: java; gutter: false" style="font-size:12px; font-family: ConfluenceInstalledFont,monospace;">
greeting=Bye
echo=Yay
destination=mock:result
</pre>
</div></div>


<h3><a name="UsingPropertyPlaceholder-BridgingSpringandCamelpropertyplaceholders"></a>Bridging Spring and Camel property placeholders</h3>
<p><b>Available as of Camel 2.10</b></p>

<p>The Spring Framework does not allow 3rd party frameworks such as Apache Camel to seamless hook into the Spring property placeholder mechanism. However you can easily bridge Spring and Camel by declaring a Spring bean with the type <tt>org.apache.camel.spring.spi.BridgePropertyPlaceholderConfigurer</tt>, which is a Spring <tt>org.springframework.beans.factory.config.PropertyPlaceholderConfigurer</tt> type. </p>

<p>To bridge Spring and Camel you must define a single bean as shown below:</p>
<div class="code panel" style="border-width: 1px;"><div class="codeHeader panelHeader" style="border-bottom-width: 1px;"><b>Bridging Spring and Camel property placeholders</b></div><div class="codeContent panelContent">
<script type="syntaxhighlighter" class="theme: Default; brush: xml; gutter: false"><![CDATA[

&lt;!-- bridge spring property placeholder with Camel --&gt;
&lt;!-- you must NOT use the &lt;context:property-placeholder at the same time, only this bridge bean --&gt;
&lt;bean id="bridgePropertyPlaceholder" class="org.apache.camel.spring.spi.BridgePropertyPlaceholderConfigurer"&gt;
  &lt;property name="location" value="classpath:org/apache/camel/component/properties/cheese.properties"/&gt;
&lt;/bean&gt;

]]></script>
</div></div>

<p>You <b>must not</b> use the spring &lt;context:property-placeholder&gt; namespace at the same time; this is not possible.</p>

<p>After declaring this bean, you can define property placeholders using both the Spring style, and the Camel style within the &lt;camelContext&gt; tag as shown below:</p>
<div class="code panel" style="border-width: 1px;"><div class="codeHeader panelHeader" style="border-bottom-width: 1px;"><b>Using bridge property placeholders</b></div><div class="codeContent panelContent">
<script type="syntaxhighlighter" class="theme: Default; brush: xml; gutter: false"><![CDATA[

&lt;!-- a bean that uses Spring property placeholder --&gt;
&lt;!-- the ${hi} is a spring property placeholder --&gt;
&lt;bean id="hello" class="org.apache.camel.component.properties.HelloBean"&gt;
  &lt;property name="greeting" value="${hi}"/&gt;
&lt;/bean&gt;

&lt;camelContext xmlns="http://camel.apache.org/schema/spring"&gt;
  &lt;!-- in this route we use Camels property placeholder {{ }} style --&gt;
  &lt;route&gt;
    &lt;from uri="direct:{{cool.bar}}"/&gt;
    &lt;bean ref="hello"/&gt;
    &lt;to uri="{{cool.end}}"/&gt;
  &lt;/route&gt;
&lt;/camelContext&gt;

]]></script>
</div></div>

<p>Notice how the hello bean is using pure Spring property placeholders using the ${ } notation. And in the Camel routes we use the Camel placeholder notation with {{ }}.</p>

<h4><a name="UsingPropertyPlaceholder-ClashingSpringpropertyplaceholderswithCamelsSimplelanguage"></a>Clashing Spring property placeholders with Camels <a href="/confluence/display/CAMEL/Simple" title="Simple">Simple</a> language</h4>
<p>Take notice when using Spring bridging placeholder then the spring ${ } syntax clashes with the <a href="/confluence/display/CAMEL/Simple" title="Simple">Simple</a> in Camel, and therefore take care. For example:</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
<pre class="theme: Default; brush: java; gutter: false" style="font-size:12px; font-family: ConfluenceInstalledFont,monospace;">
&lt;setHeader headerName="Exchange.FILE_NAME"&gt;
  &lt;simple&gt;{{file.rootdir}}/${in.header.CamelFileName}&lt;/simple&gt;
&lt;/setHeader&gt;
</pre>
</div></div>
<p>clashes with Spring property placeholders, and you should use $simple{ } to indicate using the <a href="/confluence/display/CAMEL/Simple" title="Simple">Simple</a> language in Camel.</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
<pre class="theme: Default; brush: java; gutter: false" style="font-size:12px; font-family: ConfluenceInstalledFont,monospace;">
&lt;setHeader headerName="Exchange.FILE_NAME"&gt;
  &lt;simple&gt;{{file.rootdir}}/$simple{in.header.CamelFileName}&lt;/simple&gt;
&lt;/setHeader&gt;
</pre>
</div></div>

<p>An alternative is to configure the <tt>PropertyPlaceholderConfigurer</tt> with <tt>ignoreUnresolvablePlaceholders</tt> option to <tt>true</tt>.</p>


<h3><a name="UsingPropertyPlaceholder-OverridingpropertiesfromCameltestkit"></a>Overriding properties from Camel test kit</h3>
<p><b>Available as of Camel 2.10</b></p>

<p>When <a href="/confluence/display/CAMEL/Testing" title="Testing">Testing</a> with Camel and using the <a href="/confluence/display/CAMEL/Properties" title="Properties">Properties</a> component, you may want to be able to provide the properties to be used from directly within the unit test source code.<br/>
This is now possible from Camel 2.10 onwards, as the Camel test kits, eg <tt>CamelTestSupport</tt> class offers the following methods</p>
<ul class="alternate" type="square">
	<li>useOverridePropertiesWithPropertiesComponent</li>
	<li>ignoreMissingLocationWithPropertiesComponent</li>
</ul>


<p>So for example in your unit test classes, you can override the <tt>useOverridePropertiesWithPropertiesComponent</tt> method and return a <tt>java.util.Properties</tt> that contains the properties which should be preferred to be used.</p>
<div class="code panel" style="border-width: 1px;"><div class="codeHeader panelHeader" style="border-bottom-width: 1px;"><b>Providing properties from within unit test source</b></div><div class="codeContent panelContent">
<script type="syntaxhighlighter" class="theme: Default; brush: java; gutter: false"><![CDATA[
// override this method to provide our custom properties we use in this unit test
@Override
protected Properties useOverridePropertiesWithPropertiesComponent() {
    Properties extra = new Properties();
    extra.put("destination", "mock:extra");
    extra.put("greeting", "Bye");
    return extra;
}
]]></script>
</div></div>

<p>This can be done from any of the Camel Test kits, such as camel-test, camel-test-spring, and camel-test-blueprint.</p>

<p>The <tt>ignoreMissingLocationWithPropertiesComponent</tt> can be used to instruct Camel to ignore any locations which was not discoverable, for example if you run the unit test, in an environment that does not have access to the location of the properties. </p>


<h3><a name="UsingPropertyPlaceholder-Using@PropertyInject"></a>Using @PropertyInject</h3>
<p><b>Available as of Camel 2.12</b></p>

<p>Camel allows to inject property placeholders in POJOs using the @PropertyInject annotation which can be set on fields and setter methods.<br/>
For example you can use that with <tt>RouteBuilder</tt> classes, such as shown below:</p>

<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
<pre class="theme: Default; brush: java; gutter: false" style="font-size:12px; font-family: ConfluenceInstalledFont,monospace;">
public class MyRouteBuilder extends RouteBuilder {

    @PropertyInject("hello")
    private String greeting;

    @Override
    public void configure() throws Exception {
        from("direct:start")
            .transform().constant(greeting)
            .to("{{result}}");
    }

}
</pre>
</div></div>

<p>Notice we have annotated the greeting field with @PropertyInject and define it to use the key "hello". Camel will then lookup the property with this key and inject its value, converted to a String type.</p>

<p>You can also use multiple placeholders and text in the key, for example we can do:</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
<pre class="theme: Default; brush: java; gutter: false" style="font-size:12px; font-family: ConfluenceInstalledFont,monospace;">
    @PropertyInject("Hello {{name}} how are you?")
    private String greeting;
</pre>
</div></div>

<p>This will lookup the placeholder with they key "name".</p>

<p>You can also add a default value if the key does not exists, such as:</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
<pre class="theme: Default; brush: java; gutter: false" style="font-size:12px; font-family: ConfluenceInstalledFont,monospace;">
    @PropertyInject("myTimeout", default = "5000")
    private int timeout;
</pre>
</div></div>
    </div>
        <div id="commentsSection" class="wiki-content pageSection">
        <div style="float: right;" class="grey">
                        <a href="https://cwiki.apache.org/confluence/users/removespacenotification.action?spaceKey=CAMEL">Stop watching space</a>
            <span style="padding: 0px 5px;">|</span>
                <a href="https://cwiki.apache.org/confluence/users/editmyemailsettings.action">Change email notification preferences</a>
</div>
        <a href="https://cwiki.apache.org/confluence/display/CAMEL/Using+PropertyPlaceholder">View Online</a>
        |
        <a href="https://cwiki.apache.org/confluence/pages/diffpagesbyversion.action?pageId=13271723&revisedVersion=24&originalVersion=23">View Changes</a>
                |
        <a href="https://cwiki.apache.org/confluence/display/CAMEL/Using+PropertyPlaceholder?showComments=true&amp;showCommentArea=true#addcomment">Add Comment</a>
            </div>
</div>
</div>
</div>
</div>
</body>
</html>

Mime
View raw message