Author: buildbot
Date: Fri Jan 6 16:20:47 2017
New Revision: 1004271
Log:
Production update by buildbot for camel
Modified:
websites/production/camel/content/book-cookbook.html
websites/production/camel/content/book-in-one-page.html
websites/production/camel/content/book-languages-appendix.html
websites/production/camel/content/cache/main.pageCache
websites/production/camel/content/pojo-producing.html
websites/production/camel/content/simple.html
Modified: websites/production/camel/content/book-cookbook.html
==============================================================================
--- websites/production/camel/content/book-cookbook.html (original)
+++ websites/production/camel/content/book-cookbook.html Fri Jan 6 16:20:47
2017
@@ -720,17 +720,8 @@ Camel uses this algorithm to find the ge
<p>Using the @Consume annotations are simpler when you are creating a simple
route with a single well defined input URI. </p>
<p>However if you require more complex routes or the same bean method needs to
be invoked from many places then please use the routing <a shape="rect"
href="dsl.html">DSL</a> as shown above.</p>
-There are two different ways to send messages to any Camel <a shape="rect"
href="endpoint.html">Endpoint</a> from a POJO
-
-<h4 id="Bookcookbook-@EndpointInject">@EndpointInject</h4>
-
-<p>To allow sending of messages from POJOs you can use the <a shape="rect"
class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/EndpointInject.html";>@EndpointInject</a>
annotation. This will inject a <a shape="rect" class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/ProducerTemplate.html";>ProducerTemplate</a>
so that the bean can participate in message exchanges.</p>
-
-<p>e.g. lets send a message to the <strong>foo.bar</strong> queue in <a
shape="rect" href="activemq.html">ActiveMQ</a> at some point</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[
-
-public class Foo {
+There are two different ways to send messages to any Camel <a shape="rect"
href="endpoint.html">Endpoint</a> from a POJO<h4
id="Bookcookbook-@EndpointInject"><code>@EndpointInject</code></h4><p>To allow
sending of messages from POJOs you can use the <a shape="rect"
class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/EndpointInject.html";>@EndpointInject</a>
annotation. This will inject a <a shape="rect" class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/ProducerTemplate.html";>ProducerTemplate</a>
so that the bean can participate in message exchanges.</p><p>Example: send a
message to the <strong><code>foo.bar</code></strong> ActiveMQ queue:</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[public class Foo {
@EndpointInject(uri="activemq:foo.bar")
ProducerTemplate producer;
@@ -741,21 +732,8 @@ public class Foo {
}
}
]]></script>
-</div></div>
-
-<p>The downside of this is that your code is now dependent on a Camel API, the
ProducerTemplate. The next section describes how to remove this</p>
-
-<div class="confluence-information-macro
confluence-information-macro-tip"><span class="aui-icon aui-icon-small
aui-iconfont-approve confluence-information-macro-icon"></span><div
class="confluence-information-macro-body">
-<p>See <a shape="rect" href="pojo-consuming.html">POJO Consuming</a> for how
to use a property on the bean as endpoint configuration, eg using the
<code>property</code> attribute on @Produce, @EndpointInject.</p></div></div>
-
-<h3 id="Bookcookbook-HidingtheCamelAPIsfromyourcodeusing@Produce">Hiding the
Camel APIs from your code using @Produce</h3>
-
-<p>We recommend <a shape="rect" href="hiding-middleware.html">Hiding
Middleware</a> APIs from your application code so the next option might be more
suitable.<br clear="none">
- You can add the @Produce annotation to an injection point (a field or
property setter) using a ProducerTemplate <strong>or</strong> using some
interface you use in your business logic. e.g.</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[
-public interface MyListener {
+</div></div><p>The downside of this is that your code is now dependent on a
Camel API, the <strong><code>ProducerTemplate</code></strong>. The next section
describes how to remove this dependency.</p><div
class="confluence-information-macro confluence-information-macro-tip"><span
class="aui-icon aui-icon-small aui-iconfont-approve
confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>See <a shape="rect"
href="pojo-consuming.html">POJO Consuming</a> for how to use a property on the
bean as endpoint configuration, e.g., using the
<strong><code>property</code></strong> attribute on
<strong><code>@Produce</code></strong>,
<strong><code>@EndpointInject</code></strong>.</p></div></div><h3
id="Bookcookbook-HidingtheCamelAPIsFromYourCodeUsing@Produce">Hiding the Camel
APIs From Your Code Using <code>@Produce</code></h3><p>We recommend <a
shape="rect" href="hiding-middleware.html">Hiding Middleware</a> APIs from your
application code so the next opt
ion might be more suitable. You can add
the <strong><code>@Produce</code></strong> annotation to an injection
point (a field or property setter) using
a <strong><code>ProducerTemplate</code></strong> <strong>or</strong> using
some interface you use in your business logic. 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[public interface MyListener {
String sayHello(String name);
}
@@ -769,11 +747,7 @@ public class MyBean {
}
}
]]></script>
-</div></div>
-
-<p>Here Camel will automatically inject a smart client side proxy at the
@Produce annotation - an instance of the MyListener instance. When we invoke
methods on this interface the method call is turned into an object and using
the Camel <a shape="rect" href="spring-remoting.html">Spring Remoting</a>
mechanism it is sent to the endpoint - in this case the <a shape="rect"
href="activemq.html">ActiveMQ</a> endpoint to queue <strong>foo</strong>; then
the caller blocks for a response.</p>
-
-<p>If you want to make asynchronous message sends then use <a shape="rect"
href="using-exchange-pattern-annotations.html">an @InOnly annotation on the
injection point</a>.</p>
+</div></div><p>Here Camel will automatically inject a smart client side proxy
at the <strong><code>@Produce</code></strong> annotation - an instance of
the <strong><code>MyListener</code></strong> instance. When we invoke
methods on this interface the method call is turned into an object and using
the Camel <a shape="rect" href="spring-remoting.html">Spring Remoting</a>
mechanism it is sent to the endpoint - in this case the <a shape="rect"
href="activemq.html">ActiveMQ</a> endpoint to queue
<strong><code>foo</code></strong>; then the caller blocks for a
response.</p><p>If you want to make asynchronous message sends then use <a
shape="rect" href="using-exchange-pattern-annotations.html">an @InOnly
annotation on the injection point</a>.</p>
<h2 id="Bookcookbook-@RecipientListAnnotation">@RecipientList Annotation</h2>
<p>We support the use of @RecipientList on a bean method to easily create a
dynamic <a shape="rect" href="recipient-list.html">Recipient List</a> using a
Java method.</p>
