Author: buildbot
Date: Fri Jun 9 20:23:27 2017
New Revision: 1013717
Log:
Production update by buildbot for activemq
Modified:
websites/production/activemq/content/broker-camel-component.html
websites/production/activemq/content/cache/main.pageCache
Modified: websites/production/activemq/content/broker-camel-component.html
==============================================================================
--- websites/production/activemq/content/broker-camel-component.html (original)
+++ websites/production/activemq/content/broker-camel-component.html Fri Jun 9
20:23:27 2017
@@ -90,7 +90,7 @@
<to uri="broker:queue:test.broker.component.queue"/>
</route>
</pre>
-</div></div><p>Notes:</p><ul><li>A broker component only adds an intercept
into the broker if its started - so the broker component will not add any
overhead to the running broker until its used - and then the overhead will be
trivial.</li><li>Messages are intercepted by the broker component when they
have been received by the broker - but before they are processed (persisted or
routed to a destination).</li><li>The <strong><code>IN</code></strong>
message on the Exchange is a <strong><code>CamelMessage</code></strong>, but
also a JMS Message (messages routed through ActiveMQ from STOMP/MQTT/AMQP etc.
are always translated into JMS messages).</li><li>W<a shape="rect"
class="external-link"
href="http://activemq.apache.org/wildcards.html";>ildcards</a> can be used on a
destination to intercept messages from destinations matching the
wildcard.</li><li>After the intercept, you have to explicitly send the message
back to the broker component - this allows you to either drop select me
ssages (by not sending) - or, like in the above case - re-route the message to
a different destination.<br clear="none"><br clear="none"></li></ul><div
class="confluence-information-macro confluence-information-macro-warning"><span
class="aui-icon aui-icon-small aui-iconfont-error
confluence-information-macro-icon"></span><div
class="confluence-information-macro-body">There is one deliberate caveat
though, only intercepted messages can be sent to
a <strong><code>broker</code></strong> component. For example, routing a
Camel message from another Component e.g. <strong><code>file</code></strong>,
will result in an error.</div></div><p>Extra classes that have been added to
the <strong><code>activemq-broker</code></strong> package to support
the <strong><code>broker</code></strong> component. They allow the state
of the running broker to be interrogated without using JMX. These classes
are:</p><ul><li><a shape="rect" class="external-link"
href="http://activemq.apache.org/
maven/5.9.0/apidocs/org/apache/activemq/broker/view/MessageBrokerView.html">MessageBrokerView</a>
- provides methods to retrieve statistics on a the broker</li><li>From the
MessageBrokerView - you can retrieve a <a shape="rect" class="external-link"
href="http://activemq.apache.org/maven/5.9.0/apidocs/org/apache/activemq/broker/view/BrokerDestinationView.html";>BrokerDestinationView</a>
for a particular destination.</li></ul><h3
id="BrokerCamelComponent-Example">Example</h3><p>How to route messages when a
destination's queue depth has reached a certain limit:</p><div class="code
panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p>Notes:</p><ul><li>A broker component only adds an intercept
into the broker if its started - so the broker component will not add any
overhead to the running broker until its used - and then the overhead will be
trivial.</li><li>Messages are intercepted by the broker component when they
have been received by the broker - but before they are processed (persisted or
routed to a destination).</li><li>The <strong><code>IN</code></strong>
message on the Exchange is a <strong><code>CamelMessage</code></strong>, but
also a JMS Message (messages routed through ActiveMQ from STOMP/MQTT/AMQP etc.
are always translated into JMS messages).</li><li>W<a shape="rect"
class="external-link"
href="http://activemq.apache.org/wildcards.html";>ildcards</a> can be used on a
destination to intercept messages from destinations matching the
wildcard.</li><li>After the intercept, you have to explicitly send the message
back to the broker component - this allows you to either drop select me
ssages (by not sending) - or, like in the above case - re-route the message to
a different destination.<br clear="none"><br clear="none"></li></ul><div
class="confluence-information-macro confluence-information-macro-warning"><span
class="aui-icon aui-icon-small aui-iconfont-error
confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>There is one deliberate caveat
though, only intercepted messages can be sent to
a <strong><code>broker</code></strong> component. For example, routing a
Camel message from another Component e.g. <strong><code>file</code></strong>,
will result in an error.</p></div></div><p>Extra classes that have been added
to the <strong><code>activemq-broker</code></strong> package to support
the <strong><code>broker</code></strong> component. They allow the state
of the running broker to be interrogated without using JMX. These classes
are:</p><ul><li><a shape="rect" class="external-link" href="http://activemq.apac
he.org/maven/5.9.0/apidocs/org/apache/activemq/broker/view/MessageBrokerView.html">org.apache.activemq.broker.view.MessageBrokerView</a>
- provides methods to retrieve statistics on a the broker</li><li>From
the <strong><code>org.apache.activemq.broker.view.MessageBrokerView</code></strong>
- you can retrieve a <a shape="rect" class="external-link"
href="http://activemq.apache.org/maven/5.9.0/apidocs/org/apache/activemq/broker/view/BrokerDestinationView.html";>org.apache.activemq.broker.view.BrokerDestinationView</a>
for a particular destination.</li></ul><h3
id="BrokerCamelComponent-Example">Example</h3><p>How to route messages when a
destination's queue depth has reached a certain limit:</p><div class="code
panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<pre class="brush: xml; gutter: false; theme: Default"
style="font-size:12px;"><camelContext id="camel" trace="false"
xmlns="http://camel.apache.org/schema/spring">
<route id="routeAboveQueueLimitTest">
<from uri="broker:queue:test.broker.queue"/>
Modified: websites/production/activemq/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
