You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by bu...@apache.org on 2016/07/08 23:18:20 UTC
svn commit: r992370 [14/14] - in /websites/production/camel/content: ./
cache/
Modified: websites/production/camel/content/using-propertyplaceholder.html
==============================================================================
--- websites/production/camel/content/using-propertyplaceholder.html (original)
+++ websites/production/camel/content/using-propertyplaceholder.html Fri Jul 8 23:18:19 2016
@@ -192,8 +192,7 @@ from("direct:start")
.transform().simple("Hi ${body}. ${properties:com/mycompany/bar.properties:bar.quote}.");
]]></script>
</div></div><h3 id="UsingPropertyPlaceholder-AdditionalpropertyplaceholdersupportedinSpringXML">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 <code><package>, <packageScan>, <contextScan>, <jmxAgent>, <endpoint>, <routeBuilder>, <proxy></code> and the others.</p><p>The example below has property placeholder in the <jmxAgent> tag:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-<camelContext xmlns="http://camel.apache.org/schema/spring">
+<script class="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<camelContext xmlns="http://camel.apache.org/schema/spring">
<propertyPlaceholder id="properties" location="org/apache/camel/spring/jmx.properties"/>
<!-- we can use propery placeholders when we define the JMX agent -->
@@ -208,11 +207,9 @@ from("direct:start")
<to uri="mock:result"/>
</route>
-</camelContext>
-]]></script>
-</div></div>You can also define property placeholders in the various attributes on the <camelContext> tag such as <code>trace</code> as shown here:<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-<camelContext trace="{{foo.trace}}" xmlns="http://camel.apache.org/schema/spring">
+</camelContext>]]></script>
+</div></div><p>You can also define property placeholders in the various attributes on the <camelContext> tag such as <code>trace</code> as shown here:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<camelContext trace="{{foo.trace}}" xmlns="http://camel.apache.org/schema/spring">
<propertyPlaceholder id="properties" location="org/apache/camel/spring/processor/myprop.properties"/>
<template id="camelTemplate" defaultEndpoint="{{foo.cool}}"/>
@@ -224,8 +221,7 @@ from("direct:start")
</setHeader>
<to uri="mock:result"/>
</route>
-</camelContext>
-]]></script>
+</camelContext>]]></script>
</div></div><h3 id="UsingPropertyPlaceholder-OverridingapropertysettingusingaJVMSystemProperty">Overriding a property setting using a JVM System Property</h3><p><strong>Available as of Camel 2.5</strong><br clear="none"> 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 pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[PropertiesComponent pc = context.getComponent("properties", PropertiesComponent.class);
pc.setCache(false);
@@ -253,8 +249,7 @@ System.clearProperty("cool.result&q
assertMockEndpointsSatisfied();
]]></script>
</div></div><h3 id="UsingPropertyPlaceholder-UsingpropertyplaceholdersforanykindofattributeintheXMLDSL">Using property placeholders for any kind of attribute in the XML DSL</h3><p><strong>Available as of Camel 2.7</strong></p><div class="confluence-information-macro confluence-information-macro-information"><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>If you use OSGi Blueprint then this only works from <strong>2.11.1</strong> or <strong>2.10.5</strong> onwards.</p></div></div><p>Previously it was only the <code>xs:string</code> type attributes in the XML DSL that support placeholders. For example often a timeout attribute would be a <code>xs:int</code> 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 <code>prop</code> prefix for the namespace <c
ode><a shape="rect" class="external-link" href="http://camel.apache.org/schema/placeholder">http://camel.apache.org/schema/placeholder</a></code> by which we can use the <code>prop</code> prefix in the attributes in the XML DSLs. Notice how we use that in the <a shape="rect" href="multicast.html">Multicast</a> to indicate that the option <code>stopOnException</code> should be the value of the placeholder with the key "stop".</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-<beans xmlns="http://www.springframework.org/schema/beans"
+<script class="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<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="
@@ -287,19 +282,16 @@ assertMockEndpointsSatisfied();
</camelContext>
-</beans>
-]]></script>
-</div></div>In our properties file we have the value defined as<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</beans>]]></script>
+</div></div><p>In our properties file we have the value defined as</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[stop=true
]]></script>
</div></div><h3 id="UsingPropertyPlaceholder-UsingpropertyplaceholderintheJavaDSL">Using property placeholder in the Java DSL</h3><p><strong>Available as of Camel 2.7</strong></p><p>Likewise we have added support for defining placeholders in the Java DSL using the new <code>placeholder</code> DSL as shown in the following equivalent example:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![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>
+<script class="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter"><![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 id="UsingPropertyPlaceholder-UsingBlueprintpropertyplaceholderwithCamelroutes">Using Blueprint property placeholder with Camel routes</h3><p><strong>Available as of Camel 2.7</strong></p><p>Camel supports <a shape="rect" href="using-osgi-blueprint-with-camel.html">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="error"><span class="error">Error formatting macro: snippet: java.lang.IndexOutOfBoundsException: Index: 20, Size: 20</span> </div>By default Camel detects and uses OSGi blueprint property placeholder service. You can disable this by setting the attribute <code>useBlueprintPropertyResolver</code> to false on the <code><camelContext></code> definition.<div class="confluence-information-macro confluence-information-macro-information"><p class="title">About placeholder syntaxes
</p><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>Notice how we can use the Camel syntax for placeholders {{ }} in the Camel route, which will lookup the value from OSGi blueprint.<br clear="none"> The blueprint syntax for placeholders is ${ }. So outside the <camelContext> you must use the ${ } syntax. Where as inside <camelContext> you must use {{ }} syntax.<br clear="none"> OSGi blueprint allows you to configure the syntax, so you can actually align those if you want.</p></div></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 <propertyPlaceholder> as shown in the example below:</p><div class="error"><span class="error">Error formatting macro: snippet: java.lang.IndexOutOfBoundsException: Index: 20, Size: 20</span> </div>Notice how we use the <code>blueprint</code> 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:<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[location="blueprint:myblueprint.placeholder,classpath:myproperties.properties"
]]></script>
Modified: websites/production/camel/content/xml-reference.html
==============================================================================
--- websites/production/camel/content/xml-reference.html (original)
+++ websites/production/camel/content/xml-reference.html Fri Jul 8 23:18:19 2016
@@ -84,7 +84,7 @@
<tbody>
<tr>
<td valign="top" width="100%">
[... 6 lines stripped ...]
Modified: websites/production/camel/content/yammer.html
==============================================================================
--- websites/production/camel/content/yammer.html (original)
+++ websites/production/camel/content/yammer.html Fri Jul 8 23:18:19 2016
@@ -85,81 +85,35 @@
<tbody>
<tr>
<td valign="top" width="100%">
-<div class="wiki-content maincontent"><h2 id="Yammer-Yammer">Yammer</h2>
-<p><strong>Available as of Camel 2.12</strong></p>
-
-<p>The Yammer component allows you to interact with the <a shape="rect" class="external-link" href="https://www.yammer.com" rel="nofollow">Yammer</a> enterprise social network. Consuming messages, users, and user relationships is supported as well as creating new messages.</p>
-
-<p>Yammer uses OAuth 2 for all client application authentication. In order to use camel-yammer with your account, you'll need to create a new application within Yammer and grant the application access to your account. Finally, generate your access token. More details are at <a shape="rect" class="external-link" href="https://developer.yammer.com/authentication/" rel="nofollow">https://developer.yammer.com/authentication/</a></p>
-
-<p>Maven users will need to add the following dependency to their pom.xml for this component:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-<dependency>
+<div class="wiki-content maincontent"><h2 id="Yammer-Yammer">Yammer</h2><p><strong>Available as of Camel 2.12</strong></p><p>The Yammer component allows you to interact with the <a shape="rect" class="external-link" href="https://www.yammer.com" rel="nofollow">Yammer</a> enterprise social network. Consuming messages, users, and user relationships is supported as well as creating new messages.</p><p>Yammer uses OAuth 2 for all client application authentication. In order to use camel-yammer with your account, you'll need to create a new application within Yammer and grant the application access to your account. Finally, generate your access token. More details are at <a shape="rect" class="external-link" href="https://developer.yammer.com/v1.0/docs/authentication" rel="nofollow">https://developer.yammer.com/v1.0/docs/authentication</a></p><p>Maven users will need to add the following dependency to their pom.xml for this component:</p><div class="code panel pdl" style="border-width: 1p
x;"><div class="codeContent panelContent pdl">
+<script class="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-yammer</artifactId>
<version>${camel-version}</version>
</dependency>
]]></script>
-</div></div>
-
-<h3 id="Yammer-URIformat">URI format</h3>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-yammer:[function]?[options]
+</div></div><h3 id="Yammer-URIformat">URI format</h3><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[yammer:[function]?[options]
]]></script>
-</div></div>
-
-<h3 id="Yammer-YammerComponent">YammerComponent</h3>
-
-<p>The yammer component can be configured with the Yammer account settings which are mandatory to configure before using. You can also configure these options directly in the endpoint.</p>
-<div class="confluenceTableSmall">
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Option </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> consumerKey </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The consumer key </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> consumerSecret </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The consumer secret </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> accessToken </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The access token </p></td></tr></tbody></table></div>
-</div>
-
-<h3 id="Yammer-Consumingmessages">Consuming messages</h3>
-
-<p>The camel-yammer component provides several endpoints for consuming messages:</p>
-
-<div class="confluenceTableSmall">
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> URI </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><h3 id="Yammer-YammerComponent">YammerComponent</h3><p>The yammer component can be configured with the Yammer account settings which are mandatory to configure before using. You can also configure these options directly in the endpoint.</p><div class="confluenceTableSmall"><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Option</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>consumerKey</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The consumer key</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>consumerSecret</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The consumer secret</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>accessToken</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The access token</p></td></tr></tbody></table></div
></div><h3 id="Yammer-Consumingmessages">Consuming messages</h3><p>The camel-yammer component provides several endpoints for consuming messages:</p><div class="confluenceTableSmall"><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>URI</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[yammer:messages?[options]]]></script>
-</div></div> </td><td colspan="1" rowspan="1" class="confluenceTd"><p> All public messages in the user's (whose access token is being used to make the API call) Yammer network. Corresponds to "All" conversations in the Yammer web interface. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>All public messages in the user's (whose access token is being used to make the API call) Yammer network. Corresponds to "All" conversations in the Yammer web interface.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[yammer:my_feed?[options]]]></script>
-</div></div> </td><td colspan="1" rowspan="1" class="confluenceTd"><p> The user's feed, based on the selection they have made between "Following" and "Top" conversations. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The user's feed, based on the selection they have made between "Following" and "Top" conversations.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[yammer:algo?[options]]]></script>
-</div></div> </td><td colspan="1" rowspan="1" class="confluenceTd"><p> The algorithmic feed for the user that corresponds to "Top" conversations, which is what the vast majority of users will see in the Yammer web interface. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The algorithmic feed for the user that corresponds to "Top" conversations, which is what the vast majority of users will see in the Yammer web interface.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[yammer:following?[options]]]></script>
-</div></div> </td><td colspan="1" rowspan="1" class="confluenceTd"><p> The "Following" feed which is conversations involving people, groups and topics that the user is following. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The "Following" feed which is conversations involving people, groups and topics that the user is following.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[yammer:sent?[options]]]></script>
-</div></div> </td><td colspan="1" rowspan="1" class="confluenceTd"><p> All messages sent by the user. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>All messages sent by the user.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[yammer:private?[options]]]></script>
-</div></div> </td><td colspan="1" rowspan="1" class="confluenceTd"><p> Private messages received by the user. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Private messages received by the user.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[yammer:received?[options]]]></script>
-</div></div> </td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.12.1:</strong> All messages received by the user </p></td></tr></tbody></table></div>
-</div>
-
-<h4 id="Yammer-URIOptionsforconsumingmessages">URI Options for consuming messages</h4>
-<div class="confluenceTableSmall">
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Default Value </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useJson </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>false</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Set to true if you want to use raw JSON rather than converting to POJOs. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> delay </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>5000</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> in milliseconds </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> consumerKey </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowsp
an="1" class="confluenceTd"><p> Consumer Key. Can also be configured on the <code>YammerComponent</code> level instead. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> consumerSecret </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Consumer Secret. Can also be configured on the <code>YammerComponent</code> level instead. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> accessToken </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Access Token. Can also be configured on the <code>YammerComponent</code> level instead. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> limit </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>-1</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Return only the specified nu
mber of messages. Works for threaded=true and threaded=extended. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> threaded </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> threaded=true will only return the first message in each thread. This parameter is intended for apps which display message threads collapsed. threaded=extended will return the thread starter messages in order of most recently active as well as the two most recent messages, as they are viewed in the default view on the Yammer web interface. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> olderThan </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>-1</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Returns messages older than the message ID specified as a numeric string. This is useful for paginating messages. For example, if you're currently
viewing 20 messages and the oldest is number 2912, you could append "?olderThan=2912″ to your request to get the 20 messages prior to those you're seeing. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> newerThan</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>-1</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Returns messages newer than the message ID specified as a numeric string. This should be used when polling for new messages. If you're looking at messages, and the most recent message returned is 3516, you can make a request with the parameter "?newerThan=3516″ to ensure that you do not get duplicate copies of messages already on your page. </p></td></tr></tbody></table></div>
-</div>
-
-<h4 id="Yammer-Messageformat">Message format</h4>
-
-<p>All messages by default are converted to a POJO model provided in the org.apache.camel.component.yammer.model package. The original message coming from yammer is in JSON. For all message consuming & producing endpoints, a Messages object is returned. Take for example a route like:</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-from("yammer:messages?consumerKey=aConsumerKey&consumerSecret=aConsumerSecretKey&accessToken=aAccessToken").to("mock:result");
+</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.12.1:</strong> All messages received by the user</p></td></tr></tbody></table></div></div><h4 id="Yammer-URIOptionsforconsumingmessages">URI Options for consuming messages</h4><div class="confluenceTableSmall"><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Name</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Default Value</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>useJson</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Set to true if you want to use raw JSON rather than converting to POJOs.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>delay</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>500
0</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>in milliseconds</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>consumerKey</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Consumer Key. Can also be configured on the <code>YammerComponent</code> level instead.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>consumerSecret</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Consumer Secret. Can also be configured on the <code>YammerComponent</code> level instead.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>accessToken</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Access Token. Can also be configured on the <code>YammerComponent</code>
level instead.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>limit</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>-1</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Return only the specified number of messages. Works for threaded=true and threaded=extended.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>threaded</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>threaded=true will only return the first message in each thread. This parameter is intended for apps which display message threads collapsed. threaded=extended will return the thread starter messages in order of most recently active as well as the two most recent messages, as they are viewed in the default view on the Yammer web interface.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>olderThan</p></td><td colspan="1" rowspan="1" class
="confluenceTd"><p><code>-1</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Returns messages older than the message ID specified as a numeric string. This is useful for paginating messages. For example, if you're currently viewing 20 messages and the oldest is number 2912, you could append "?olderThan=2912″ to your request to get the 20 messages prior to those you're seeing.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>newerThan</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>-1</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Returns messages newer than the message ID specified as a numeric string. This should be used when polling for new messages. If you're looking at messages, and the most recent message returned is 3516, you can make a request with the parameter "?newerThan=3516″ to ensure that you do not get duplicate copies of messages already on your page.</p></td></tr></tbody></table><
/div></div><h4 id="Yammer-Messageformat">Message format</h4><p>All messages by default are converted to a POJO model provided in the org.apache.camel.component.yammer.model package. The original message coming from yammer is in JSON. For all message consuming & producing endpoints, a Messages object is returned. Take for example a route like:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[from("yammer:messages?consumerKey=aConsumerKey&consumerSecret=aConsumerSecretKey&accessToken=aAccessToken").to("mock:result");
]]></script>
-</div></div>
-
-<p>and lets say the yammer server returns:</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-{
+</div></div><p>and lets say the yammer server returns:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[{
"messages":[
{
"replied_to_id":null,
@@ -232,54 +186,24 @@ from("yammer:messages?consumerKey=a
}
]]></script>
-</div></div>
-
-<p>Camel will marshal that into a Messages object containing 2 Message objects. As shown below there is a rich object model that makes it easy to get any information you need:</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
- Exchange exchange = mock.getExchanges().get(0);
+</div></div><p>Camel will marshal that into a Messages object containing 2 Message objects. As shown below there is a rich object model that makes it easy to get any information you need:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ Exchange exchange = mock.getExchanges().get(0);
Messages messages = exchange.getIn().getBody(Messages.class);
assertEquals(2, messages.getMessages().size());
assertEquals("Testing yammer API...", messages.getMessages().get(0).getBody().getPlain());
assertEquals("(Principal Software Engineer) has #joined the redhat.com network. Take a moment to welcome Jonathan.", messages.getMessages().get(1).getBody().getPlain());
]]></script>
-</div></div>
-
-<p>That said, marshaling this data into POJOs is not free so if you need you can switch back to using pure JSON by adding the useJson=false option to your URI.</p>
-
-<h3 id="Yammer-Creatingmessages">Creating messages</h3>
-
-<p>To create a new message in the account of the current user, you can use the following URI:</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-yammer:messages?[options]
+</div></div><p>That said, marshaling this data into POJOs is not free so if you need you can switch back to using pure JSON by adding the useJson=false option to your URI.</p><h3 id="Yammer-Creatingmessages">Creating messages</h3><p>To create a new message in the account of the current user, you can use the following URI:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[yammer:messages?[options]
]]></script>
-</div></div>
-
-<p>The current Camel message body is what will be used to set the text of the Yammer message. The response body will include the new message formatted the same way as when you consume messages (i.e. as a Messages object by default). </p>
-
-<p>Take this route for instance:</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-from("direct:start").to("yammer:messages?consumerKey=aConsumerKey&consumerSecret=aConsumerSecretKey&accessToken=aAccessToken").to("mock:result");
+</div></div><p>The current Camel message body is what will be used to set the text of the Yammer message. The response body will include the new message formatted the same way as when you consume messages (i.e. as a Messages object by default).</p><p>Take this route for instance:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[from("direct:start").to("yammer:messages?consumerKey=aConsumerKey&consumerSecret=aConsumerSecretKey&accessToken=aAccessToken").to("mock:result");
]]></script>
-</div></div>
-
-<p>By sending to the direct:start endpoint a "Hi from Camel!" message body:</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
- template.sendBody("direct:start", "Hi from Camel!");
+</div></div><p>By sending to the direct:start endpoint a "Hi from Camel!" message body:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ template.sendBody("direct:start", "Hi from Camel!");
]]></script>
-</div></div>
-
-<p>a new message will be created in the current user's account on the server and also this new message will be returned to Camel and converted into a Messages object. Like when consuming messages you can interrogate the Messages object: </p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p>a new message will be created in the current user's account on the server and also this new message will be returned to Camel and converted into a Messages object. Like when consuming messages you can interrogate the Messages object:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
Exchange exchange = mock.getExchanges().get(0);
Messages messages = exchange.getIn().getBody(Messages.class);
@@ -287,55 +211,17 @@ from("direct:start").to("
assertEquals(1, messages.getMessages().size());
assertEquals("Hi from Camel!", messages.getMessages().get(0).getBody().getPlain());
]]></script>
-</div></div>
-
-<h3 id="Yammer-Retrievinguserrelationships">Retrieving user relationships</h3>
-
-<p>The camel-yammer component can retrieve user relationships:</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-yammer:relationships?[options]
+</div></div><h3 id="Yammer-Retrievinguserrelationships">Retrieving user relationships</h3><p>The camel-yammer component can retrieve user relationships:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[yammer:relationships?[options]
]]></script>
-</div></div>
-
-<h4 id="Yammer-URIOptionsforretrievingrelationships">URI Options for retrieving relationships</h4>
-<div class="confluenceTableSmall">
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Default Value </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useJson </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>false</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Set to true if you want to use raw JSON rather than converting to POJOs. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> delay </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>5000</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> in milliseconds </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> consumerKey </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowsp
an="1" class="confluenceTd"><p> Consumer Key. Can also be configured on the <code>YammerComponent</code> level instead. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> consumerSecret </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Consumer Secret. Can also be configured on the <code>YammerComponent</code> level instead. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> accessToken </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Access Token. Can also be configured on the <code>YammerComponent</code> level instead. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> userId </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>current user</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> To view the relat
ionships for a user other than the current user. </p></td></tr></tbody></table></div>
-</div>
-
-<h3 id="Yammer-Retrievingusers">Retrieving users</h3>
-
-<p>The camel-yammer component provides several endpoints for retrieving users:</p>
-
-<div class="confluenceTableSmall">
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> URI </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><h4 id="Yammer-URIOptionsforretrievingrelationships">URI Options for retrieving relationships</h4><div class="confluenceTableSmall"><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Name</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Default Value</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>useJson</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Set to true if you want to use raw JSON rather than converting to POJOs.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>delay</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>5000</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>in milliseconds</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<p>consumerKey</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Consumer Key. Can also be configured on the <code>YammerComponent</code> level instead.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>consumerSecret</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Consumer Secret. Can also be configured on the <code>YammerComponent</code> level instead.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>accessToken</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Access Token. Can also be configured on the <code>YammerComponent</code> level instead.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>userId</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>
<code>current user</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>To view the relationships for a user other than the current user.</p></td></tr></tbody></table></div></div><h3 id="Yammer-Retrievingusers">Retrieving users</h3><p>The camel-yammer component provides several endpoints for retrieving users:</p><div class="confluenceTableSmall"><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>URI</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[yammer:users?[options]]]></script>
-</div></div> </td><td colspan="1" rowspan="1" class="confluenceTd"><p> Retrieve users in the current user's Yammer network. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Retrieve users in the current user's Yammer network.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[yammer:current?[options]]]></script>
-</div></div> </td><td colspan="1" rowspan="1" class="confluenceTd"><p> View data about the current user. </p></td></tr></tbody></table></div>
-</div>
-
-<h4 id="Yammer-URIOptionsforretrievingusers">URI Options for retrieving users</h4>
-<div class="confluenceTableSmall">
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Default Value </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useJson </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>false</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Set to true if you want to use raw JSON rather than converting to POJOs. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> delay </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>5000</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> in milliseconds </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> consumerKey </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowsp
an="1" class="confluenceTd"><p> Consumer Key. Can also be configured on the <code>YammerComponent</code> level instead. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> consumerSecret </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Consumer Secret. Can also be configured on the <code>YammerComponent</code> level instead. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> accessToken </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Access Token. Can also be configured on the <code>YammerComponent</code> level instead. </p></td></tr></tbody></table></div>
-</div>
-
-<h3 id="Yammer-Usinganenricher">Using an enricher</h3>
-
-<p>It is helpful sometimes (or maybe always in the case of users or relationship consumers) to use an enricher pattern rather than a route initiated with one of the polling consumers in camel-yammer. This is because the consumers will fire repeatedly, however often you set the delay for. If you just want to look up a user's data, or grab a message at a point in time, it is better to call that consumer once and then get one with your route. </p>
-
-<p>Lets say you have a route that at some point needs to go out and fetch user data for the current user. Rather than polling for this user over and over again, use the pollEnrich DSL method:</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-from("direct:start").pollEnrich("yammer:current?consumerKey=aConsumerKey&consumerSecret=aConsumerSecretKey&accessToken=aAccessToken").to("mock:result");
+</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>View data about the current user.</p></td></tr></tbody></table></div></div><h4 id="Yammer-URIOptionsforretrievingusers">URI Options for retrieving users</h4><div class="confluenceTableSmall"><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Name</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Default Value</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>useJson</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Set to true if you want to use raw JSON rather than converting to POJOs.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>delay</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>5000</code></p></td><td colspan="1" ro
wspan="1" class="confluenceTd"><p>in milliseconds</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>consumerKey</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Consumer Key. Can also be configured on the <code>YammerComponent</code> level instead.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>consumerSecret</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Consumer Secret. Can also be configured on the <code>YammerComponent</code> level instead.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>accessToken</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Access Token. Can also be configured on the <code>YammerComponent</code> level instead.</p></td></tr></tbody
></table></div></div><h3 id="Yammer-Usinganenricher">Using an enricher</h3><p>It is helpful sometimes (or maybe always in the case of users or relationship consumers) to use an enricher pattern rather than a route initiated with one of the polling consumers in camel-yammer. This is because the consumers will fire repeatedly, however often you set the delay for. If you just want to look up a user's data, or grab a message at a point in time, it is better to call that consumer once and then get one with your route.</p><p>Lets say you have a route that at some point needs to go out and fetch user data for the current user. Rather than polling for this user over and over again, use the pollEnrich DSL method:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[from("direct:start").pollEnrich("yammer:current?consumerKey=aConsumerKey&consumerSecret=aConsumerSecretKey&accessToken=aAccessToken").to("mock:result");
]]></script>
-</div></div>
-
-<p>This will go out and fetch the current user's User object and set it as the Camel message body. </p>
-
-<h3 id="Yammer-SeeAlso">See Also</h3>
+</div></div><p>This will go out and fetch the current user's User object and set it as the Camel message body.</p><p></p><h3 id="Yammer-SeeAlso">See Also</h3>
<ul><li><a shape="rect" href="configuring-camel.html">Configuring Camel</a></li><li><a shape="rect" href="component.html">Component</a></li><li><a shape="rect" href="endpoint.html">Endpoint</a></li><li><a shape="rect" href="getting-started.html">Getting Started</a></li></ul></div>
</td>
<td valign="top">