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 2013/11/14 18:19:27 UTC
svn commit: r886645 - in /websites/production/camel/content:
bean-injection.html bean-integration.html book-cookbook.html
book-in-one-page.html cache/main.pageCache camel-2130-release.html
Author: buildbot
Date: Thu Nov 14 17:19:27 2013
New Revision: 886645
Log:
Production update by buildbot for camel
Modified:
websites/production/camel/content/bean-injection.html
websites/production/camel/content/bean-integration.html
websites/production/camel/content/book-cookbook.html
websites/production/camel/content/book-in-one-page.html
websites/production/camel/content/cache/main.pageCache
websites/production/camel/content/camel-2130-release.html
Modified: websites/production/camel/content/bean-injection.html
==============================================================================
--- websites/production/camel/content/bean-injection.html (original)
+++ websites/production/camel/content/bean-injection.html Thu Nov 14 17:19:27 2013
@@ -36,6 +36,16 @@
<![endif]-->
+ <link href='http://camel.apache.org/styles/highlighter/styles/shCoreCamel.css' rel='stylesheet' type='text/css' />
+ <link href='http://camel.apache.org/styles/highlighter/styles/shThemeCamel.css' rel='stylesheet' type='text/css' />
+ <script src='http://camel.apache.org/styles/highlighter/scripts/shCore.js' type='text/javascript'></script>
+ <script src='http://camel.apache.org/styles/highlighter/scripts/shBrushJava.js' type='text/javascript'></script>
+ <script src='http://camel.apache.org/styles/highlighter/scripts/shBrushXml.js' type='text/javascript'></script>
+
+ <script type="text/javascript">
+ SyntaxHighlighter.defaults['toolbar'] = false;
+ SyntaxHighlighter.all();
+ </script>
<title>
Apache Camel: Bean Injection
@@ -77,10 +87,45 @@
<td valign="top" width="100%">
<div class="wiki-content maincontent"><h3><a shape="rect" name="BeanInjection-BeanInjection"></a>Bean Injection</h3>
-<p>We support the injection of various resources using @EndpointInject. This can be used to inject</p>
+<p>We support the injection of various resources using @EndpointInject or @BeanInject. This can be used to inject</p>
<ul><li><a shape="rect" href="endpoint.html" title="Endpoint">Endpoint</a> instances which can be used for testing when used with <a shape="rect" href="mock.html" title="Mock">Mock</a> endpoints; see the <a shape="rect" href="spring-testing.html" title="Spring Testing">Spring Testing</a> for an example.</li><li><a shape="rect" href="producertemplate.html" title="ProducerTemplate">ProducerTemplate</a> instances for <a shape="rect" href="pojo-producing.html" title="POJO Producing">POJO Producing</a></li><li>client side proxies for <a shape="rect" href="pojo-producing.html" title="POJO Producing">POJO Producing</a> which is a simple approach to <a shape="rect" href="spring-remoting.html" title="Spring Remoting">Spring Remoting</a></li></ul>
+
+<h4><a shape="rect" name="BeanInjection-Using@BeanInject"></a>Using @BeanInject</h4>
+
+<p>From <b>Camel 2.13</b> onwards you can inject beans (obtained from the <a shape="rect" href="registry.html" title="Registry">Registry</a>) into your beans such as <tt>RouteBuilder</tt> classes. </p>
+
+<p>For example to inject a bean named foo, you can enlist the bean in the <a shape="rect" href="registry.html" title="Registry">Registry</a> such as in a Spring XML file:</p>
+
+<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
+<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
+<bean id="foo" class="com.foo.MyFooBean"/>
+]]></script>
+</div></div>
+
+<p>And then in a Java <tt>RouteBuilder</tt> class, you can inject the bean using <tt>@BeanInject</tt> as shown below:</p>
+<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
+public class MyRouteBuilder extends RouteBuilder {
+
+ @BeanInject("foo")
+ MyFooBean foo;
+
+ public void configure() throws Exception {
+ ..
+ }
+}
+]]></script>
+</div></div>
+
+<p>If you omit the name, then Camel does a lookup by type, and injects the bean if there is exactly only one bean of that type enlisted in the <a shape="rect" href="registry.html" title="Registry">Registry</a>.</p>
+<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
+ @BeanInject
+ MyFooBean foo;
+]]></script>
+</div></div>
</div>
</td>
<td valign="top">
Modified: websites/production/camel/content/bean-integration.html
==============================================================================
--- websites/production/camel/content/bean-integration.html (original)
+++ websites/production/camel/content/bean-integration.html Thu Nov 14 17:19:27 2013
@@ -82,6 +82,15 @@
<h3><a shape="rect" name="BeanIntegration-Annotations"></a>Annotations</h3>
<p>If a bean is defined in <a shape="rect" href="spring.html" title="Spring">Spring</a> XML or scanned using the Spring component scanning mechanism and a <b><camelContext></b> is used or a <tt>CamelBeanPostProcessor</tt> then we process a number of Camel annotations to do various things such as injecting resources or producing, consuming or routing messages.</p>
+<p>The following annotations is supported and inject by Camel's <tt>CamelBeanPostProcessor</tt></p>
+
+<div class="table-wrap">
+<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"> Annotation </th><th colspan="1" rowspan="1" class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>@EndpointInject</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> To inject an endpoint, see more details at <a shape="rect" href="pojo-producing.html" title="POJO Producing">POJO Producing</a>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>@BeanInject</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.13:</b> To inject a bean obtained from the <a shape="rect" href="registry.html" title="Registry">Registry</a>. See <a shape="rect" href="bean-injection.html" title="Bean Injection">Bean Injection</a>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>@PropertyInject</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.12:</b> To inject a value using <a shape="rect"
href="using-propertyplaceholder.html" title="Using PropertyPlaceholder">property placeholder</a>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>@Produce</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> To inject a producer to send message to an endpoint. See <a shape="rect" href="pojo-producing.html" title="POJO Producing">POJO Producing</a>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>@Consume</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> To inject a consumer on a method. See <a shape="rect" href="pojo-consuming.html" title="POJO Consuming">POJO Consuming</a>. </td></tr></tbody></table>
+</div>
+
+
+<p>See more details at:</p>
+
<ul><li><a shape="rect" href="pojo-consuming.html" title="POJO Consuming">POJO Consuming</a> to consume and possibly route messages from Camel</li><li><a shape="rect" href="pojo-producing.html" title="POJO Producing">POJO Producing</a> to make it easy to produce camel messages from your POJOs</li><li><a shape="rect" href="dynamicrouter-annotation.html" title="DynamicRouter Annotation">DynamicRouter Annotation</a> for creating a <a shape="rect" href="dynamic-router.html" title="Dynamic Router">Dynamic Router</a> from a POJO method</li><li><a shape="rect" href="recipientlist-annotation.html" title="RecipientList Annotation">RecipientList Annotation</a> for creating a <a shape="rect" href="recipient-list.html" title="Recipient List">Recipient List</a> from a POJO method</li><li><a shape="rect" href="routingslip-annotation.html" title="RoutingSlip Annotation">RoutingSlip Annotation</a> for creating a <a shape="rect" href="routing-slip.html" title="Routing Slip">Routing Slip</a> for a PO
JO method</li><li><a shape="rect" href="bean-injection.html" title="Bean Injection">Bean Injection</a> to inject Camel related resources into your POJOs</li><li><a shape="rect" href="using-exchange-pattern-annotations.html" title="Using Exchange Pattern Annotations">Using Exchange Pattern Annotations</a> describes how the pattern annotations can be used to change the behaviour of method invocations with <a shape="rect" href="spring-remoting.html" title="Spring Remoting">Spring Remoting</a> or <a shape="rect" href="pojo-producing.html" title="POJO Producing">POJO Producing</a></li></ul>
Modified: websites/production/camel/content/book-cookbook.html
==============================================================================
--- websites/production/camel/content/book-cookbook.html (original)
+++ websites/production/camel/content/book-cookbook.html Thu Nov 14 17:19:27 2013
@@ -103,6 +103,15 @@
<h3><a shape="rect" name="Bookcookbook-Annotations"></a>Annotations</h3>
<p>If a bean is defined in <a shape="rect" href="spring.html" title="Spring">Spring</a> XML or scanned using the Spring component scanning mechanism and a <b><camelContext></b> is used or a <tt>CamelBeanPostProcessor</tt> then we process a number of Camel annotations to do various things such as injecting resources or producing, consuming or routing messages.</p>
+<p>The following annotations is supported and inject by Camel's <tt>CamelBeanPostProcessor</tt></p>
+
+<div class="table-wrap">
+<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"> Annotation </th><th colspan="1" rowspan="1" class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>@EndpointInject</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> To inject an endpoint, see more details at <a shape="rect" href="pojo-producing.html" title="POJO Producing">POJO Producing</a>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>@BeanInject</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.13:</b> To inject a bean obtained from the <a shape="rect" href="registry.html" title="Registry">Registry</a>. See <a shape="rect" href="bean-injection.html" title="Bean Injection">Bean Injection</a>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>@PropertyInject</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.12:</b> To inject a value using <a shape="rect"
href="using-propertyplaceholder.html" title="Using PropertyPlaceholder">property placeholder</a>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>@Produce</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> To inject a producer to send message to an endpoint. See <a shape="rect" href="pojo-producing.html" title="POJO Producing">POJO Producing</a>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>@Consume</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> To inject a consumer on a method. See <a shape="rect" href="pojo-consuming.html" title="POJO Consuming">POJO Consuming</a>. </td></tr></tbody></table>
+</div>
+
+
+<p>See more details at:</p>
+
<ul><li><a shape="rect" href="pojo-consuming.html" title="POJO Consuming">POJO Consuming</a> to consume and possibly route messages from Camel</li><li><a shape="rect" href="pojo-producing.html" title="POJO Producing">POJO Producing</a> to make it easy to produce camel messages from your POJOs</li><li><a shape="rect" href="dynamicrouter-annotation.html" title="DynamicRouter Annotation">DynamicRouter Annotation</a> for creating a <a shape="rect" href="dynamic-router.html" title="Dynamic Router">Dynamic Router</a> from a POJO method</li><li><a shape="rect" href="recipientlist-annotation.html" title="RecipientList Annotation">RecipientList Annotation</a> for creating a <a shape="rect" href="recipient-list.html" title="Recipient List">Recipient List</a> from a POJO method</li><li><a shape="rect" href="routingslip-annotation.html" title="RoutingSlip Annotation">RoutingSlip Annotation</a> for creating a <a shape="rect" href="routing-slip.html" title="Routing Slip">Routing Slip</a> for a PO
JO method</li><li><a shape="rect" href="bean-injection.html" title="Bean Injection">Bean Injection</a> to inject Camel related resources into your POJOs</li><li><a shape="rect" href="using-exchange-pattern-annotations.html" title="Using Exchange Pattern Annotations">Using Exchange Pattern Annotations</a> describes how the pattern annotations can be used to change the behaviour of method invocations with <a shape="rect" href="spring-remoting.html" title="Spring Remoting">Spring Remoting</a> or <a shape="rect" href="pojo-producing.html" title="POJO Producing">POJO Producing</a></li></ul>
@@ -496,11 +505,46 @@ doSomething(com.foo.MyOrder ${body}, boo
<p>This may change in the future.</p></td></tr></table></div>
<h3><a shape="rect" name="Bookcookbook-BeanInjection"></a>Bean Injection</h3>
-<p>We support the injection of various resources using @EndpointInject. This can be used to inject</p>
+<p>We support the injection of various resources using @EndpointInject or @BeanInject. This can be used to inject</p>
<ul><li><a shape="rect" href="endpoint.html" title="Endpoint">Endpoint</a> instances which can be used for testing when used with <a shape="rect" href="mock.html" title="Mock">Mock</a> endpoints; see the <a shape="rect" href="spring-testing.html" title="Spring Testing">Spring Testing</a> for an example.</li><li><a shape="rect" href="producertemplate.html" title="ProducerTemplate">ProducerTemplate</a> instances for <a shape="rect" href="pojo-producing.html" title="POJO Producing">POJO Producing</a></li><li>client side proxies for <a shape="rect" href="pojo-producing.html" title="POJO Producing">POJO Producing</a> which is a simple approach to <a shape="rect" href="spring-remoting.html" title="Spring Remoting">Spring Remoting</a></li></ul>
+<h4><a shape="rect" name="Bookcookbook-Using@BeanInject"></a>Using @BeanInject</h4>
+
+<p>From <b>Camel 2.13</b> onwards you can inject beans (obtained from the <a shape="rect" href="registry.html" title="Registry">Registry</a>) into your beans such as <tt>RouteBuilder</tt> classes. </p>
+
+<p>For example to inject a bean named foo, you can enlist the bean in the <a shape="rect" href="registry.html" title="Registry">Registry</a> such as in a Spring XML file:</p>
+
+<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
+<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
+<bean id="foo" class="com.foo.MyFooBean"/>
+]]></script>
+</div></div>
+
+<p>And then in a Java <tt>RouteBuilder</tt> class, you can inject the bean using <tt>@BeanInject</tt> as shown below:</p>
+<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
+public class MyRouteBuilder extends RouteBuilder {
+
+ @BeanInject("foo")
+ MyFooBean foo;
+
+ public void configure() throws Exception {
+ ..
+ }
+}
+]]></script>
+</div></div>
+
+<p>If you omit the name, then Camel does a lookup by type, and injects the bean if there is exactly only one bean of that type enlisted in the <a shape="rect" href="registry.html" title="Registry">Registry</a>.</p>
+<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
+ @BeanInject
+ MyFooBean foo;
+]]></script>
+</div></div>
+
<h3><a shape="rect" name="Bookcookbook-ParameterBindingAnnotations"></a>Parameter Binding Annotations</h3>
<div class="panelMacro"><table class="infoMacro"><colgroup span="1"><col span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1" valign="top"><img align="middle" src="https://cwiki.apache.org/confluence/images/icons/emoticons/information.gif" width="16" height="16" alt="" border="0"></td><td colspan="1" rowspan="1"><b>camel-core</b><br clear="none">The annotations below are all part of <b>camel-core</b> and thus does not require <b>camel-spring</b> or <a shape="rect" href="spring.html" title="Spring">Spring</a>. These annotations can be used with the <a shape="rect" href="bean.html" title="Bean">Bean</a> component or when invoking beans in the <a shape="rect" href="dsl.html" title="DSL">DSL</a></td></tr></table></div>
Modified: websites/production/camel/content/book-in-one-page.html
==============================================================================
--- websites/production/camel/content/book-in-one-page.html (original)
+++ websites/production/camel/content/book-in-one-page.html Thu Nov 14 17:19:27 2013
@@ -1452,6 +1452,15 @@ zeromq:(tcp|ipc)://hostname:port
<h3><a shape="rect" name="BookInOnePage-Annotations"></a>Annotations</h3>
<p>If a bean is defined in <a shape="rect" href="spring.html" title="Spring">Spring</a> XML or scanned using the Spring component scanning mechanism and a <b><camelContext></b> is used or a <tt>CamelBeanPostProcessor</tt> then we process a number of Camel annotations to do various things such as injecting resources or producing, consuming or routing messages.</p>
+<p>The following annotations is supported and inject by Camel's <tt>CamelBeanPostProcessor</tt></p>
+
+<div class="table-wrap">
+<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"> Annotation </th><th colspan="1" rowspan="1" class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>@EndpointInject</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> To inject an endpoint, see more details at <a shape="rect" href="pojo-producing.html" title="POJO Producing">POJO Producing</a>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>@BeanInject</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.13:</b> To inject a bean obtained from the <a shape="rect" href="registry.html" title="Registry">Registry</a>. See <a shape="rect" href="bean-injection.html" title="Bean Injection">Bean Injection</a>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>@PropertyInject</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.12:</b> To inject a value using <a shape="rect"
href="using-propertyplaceholder.html" title="Using PropertyPlaceholder">property placeholder</a>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>@Produce</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> To inject a producer to send message to an endpoint. See <a shape="rect" href="pojo-producing.html" title="POJO Producing">POJO Producing</a>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>@Consume</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> To inject a consumer on a method. See <a shape="rect" href="pojo-consuming.html" title="POJO Consuming">POJO Consuming</a>. </td></tr></tbody></table>
+</div>
+
+
+<p>See more details at:</p>
+
<ul><li><a shape="rect" href="pojo-consuming.html" title="POJO Consuming">POJO Consuming</a> to consume and possibly route messages from Camel</li><li><a shape="rect" href="pojo-producing.html" title="POJO Producing">POJO Producing</a> to make it easy to produce camel messages from your POJOs</li><li><a shape="rect" href="dynamicrouter-annotation.html" title="DynamicRouter Annotation">DynamicRouter Annotation</a> for creating a <a shape="rect" href="dynamic-router.html" title="Dynamic Router">Dynamic Router</a> from a POJO method</li><li><a shape="rect" href="recipientlist-annotation.html" title="RecipientList Annotation">RecipientList Annotation</a> for creating a <a shape="rect" href="recipient-list.html" title="Recipient List">Recipient List</a> from a POJO method</li><li><a shape="rect" href="routingslip-annotation.html" title="RoutingSlip Annotation">RoutingSlip Annotation</a> for creating a <a shape="rect" href="routing-slip.html" title="Routing Slip">Routing Slip</a> for a PO
JO method</li><li><a shape="rect" href="bean-injection.html" title="Bean Injection">Bean Injection</a> to inject Camel related resources into your POJOs</li><li><a shape="rect" href="using-exchange-pattern-annotations.html" title="Using Exchange Pattern Annotations">Using Exchange Pattern Annotations</a> describes how the pattern annotations can be used to change the behaviour of method invocations with <a shape="rect" href="spring-remoting.html" title="Spring Remoting">Spring Remoting</a> or <a shape="rect" href="pojo-producing.html" title="POJO Producing">POJO Producing</a></li></ul>
@@ -1845,11 +1854,46 @@ doSomething(com.foo.MyOrder ${body}, boo
<p>This may change in the future.</p></td></tr></table></div>
<h3><a shape="rect" name="BookInOnePage-BeanInjection"></a>Bean Injection</h3>
-<p>We support the injection of various resources using @EndpointInject. This can be used to inject</p>
+<p>We support the injection of various resources using @EndpointInject or @BeanInject. This can be used to inject</p>
<ul><li><a shape="rect" href="endpoint.html" title="Endpoint">Endpoint</a> instances which can be used for testing when used with <a shape="rect" href="mock.html" title="Mock">Mock</a> endpoints; see the <a shape="rect" href="spring-testing.html" title="Spring Testing">Spring Testing</a> for an example.</li><li><a shape="rect" href="producertemplate.html" title="ProducerTemplate">ProducerTemplate</a> instances for <a shape="rect" href="pojo-producing.html" title="POJO Producing">POJO Producing</a></li><li>client side proxies for <a shape="rect" href="pojo-producing.html" title="POJO Producing">POJO Producing</a> which is a simple approach to <a shape="rect" href="spring-remoting.html" title="Spring Remoting">Spring Remoting</a></li></ul>
+<h4><a shape="rect" name="BookInOnePage-Using@BeanInject"></a>Using @BeanInject</h4>
+
+<p>From <b>Camel 2.13</b> onwards you can inject beans (obtained from the <a shape="rect" href="registry.html" title="Registry">Registry</a>) into your beans such as <tt>RouteBuilder</tt> classes. </p>
+
+<p>For example to inject a bean named foo, you can enlist the bean in the <a shape="rect" href="registry.html" title="Registry">Registry</a> such as in a Spring XML file:</p>
+
+<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
+<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
+<bean id="foo" class="com.foo.MyFooBean"/>
+]]></script>
+</div></div>
+
+<p>And then in a Java <tt>RouteBuilder</tt> class, you can inject the bean using <tt>@BeanInject</tt> as shown below:</p>
+<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
+public class MyRouteBuilder extends RouteBuilder {
+
+ @BeanInject("foo")
+ MyFooBean foo;
+
+ public void configure() throws Exception {
+ ..
+ }
+}
+]]></script>
+</div></div>
+
+<p>If you omit the name, then Camel does a lookup by type, and injects the bean if there is exactly only one bean of that type enlisted in the <a shape="rect" href="registry.html" title="Registry">Registry</a>.</p>
+<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
+ @BeanInject
+ MyFooBean foo;
+]]></script>
+</div></div>
+
<h3><a shape="rect" name="BookInOnePage-ParameterBindingAnnotations"></a>Parameter Binding Annotations</h3>
<div class="panelMacro"><table class="infoMacro"><colgroup span="1"><col span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1" valign="top"><img align="middle" src="https://cwiki.apache.org/confluence/images/icons/emoticons/information.gif" width="16" height="16" alt="" border="0"></td><td colspan="1" rowspan="1"><b>camel-core</b><br clear="none">The annotations below are all part of <b>camel-core</b> and thus does not require <b>camel-spring</b> or <a shape="rect" href="spring.html" title="Spring">Spring</a>. These annotations can be used with the <a shape="rect" href="bean.html" title="Bean">Bean</a> component or when invoking beans in the <a shape="rect" href="dsl.html" title="DSL">DSL</a></td></tr></table></div>
Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/camel/content/camel-2130-release.html
==============================================================================
--- websites/production/camel/content/camel-2130-release.html (original)
+++ websites/production/camel/content/camel-2130-release.html Thu Nov 14 17:19:27 2013
@@ -94,7 +94,7 @@
<p>Welcome to the 2.13.0 release which approx XXX issues resolved (new features, improvements and bug fixes such as...)</p>
-<ul><li>The MBean names registered by <a shape="rect" href="camel-jmx.html" title="Camel JMX">Camel JMX</a> no longer include the hostname in the <tt>context</tt> part, eg before <tt>context=myHost/myCamelId</tt> and now after <tt>context=myCamelId</tt>. Having the hostname in the MBean name does not bring much value, and in fact makes things more complicated as the mbean name changes depending on the host running Camel.</li><li>When using multiple OSGi Blueprint <cm:property-placeholder>'s then Camel now favors using non-default placeholders, or the last property-placeholder defined in the Blueprint XML file. This allows for example to define default properties in one placeholder, and override these values in other placeholders.</li><li><a shape="rect" href="ftp2.html" title="FTP2">FTP</a> consumer allow to download a single named file without using the FTP LIST command. This allows to download a known file from a FTP server even when the user account does not have permission
to do FTP LIST command.</li><li><a shape="rect" href="ftp2.html" title="FTP2">FTP</a> consumer allow to ignore file not found or insufficient file permission errors.</li><li><a shape="rect" href="data-format.html" title="Data Format">Data Format</a> using marshal now leverages <a shape="rect" href="stream-caching.html" title="Stream caching">Stream caching</a> out of the box if enabled, which allows to marshal big streams and spool to disk, instead of being pure in-memory based.</li><li>Improved using <a shape="rect" href="bean.html" title="Bean">Bean</a> when the bean is looked up in the <a shape="rect" href="registry.html" title="Registry">Registry</a>, when using concurrent processing in the route.</li><li>Added <tt>cache</tt> option to <tt>beanRef</tt> and <tt><bean></tt> in the DSL. This avoids looking up the <a shape="rect" href="bean.html" title="Bean">Bean</a> from the <a shape="rect" href="registry.html" title="Registry">Registry</a> on each usage; this can safely be
done for singleton beans.</li><li>Configuring <a shape="rect" href="data-format.html" title="Data Format">Data Format</a>s in XML attributes now supports reference lookup using the # syntax, eg <tt><jaxb xmlStreamWriterWrapper="#myWriterWrapper" ..></tt></li><li><a shape="rect" href="jdbc.html" title="JDBC">JDBC</a> component now also support <tt>outputType</tt> to specify the expected output as either a List or single Object. As well allow to map to a bean using a <tt>BeanRowMapper</tt> to control the mapping of ROW names to bean properties.</li><li>Both <a shape="rect" href="quartz.html" title="Quartz">Quartz</a> as well as <a shape="rect" href="quartz2.html" title="Quartz2">Quartz2</a> based <a shape="rect" href="scheduledroutepolicy.html" title="ScheduledRoutePolicy">ScheduledRoutePolicy</a> has been improved to better support cluster setups (e.g. to not schedule jobs being already scheduled through another node inside a given cluster).</li><li>Reduced the work the <a sha
pe="rect" href="aggregator2.html" title="Aggregator2">Aggregate</a> EIP does while holding a lock during aggregation, which can lead to improved performance in some use-cases.</li><li><tt>JndiRegistry</tt> now implements all the find methods.</li><li><a shape="rect" href="vm.html" title="VM">VM</a> component now supports <tt>multipleConsumers=true</tt> across deployment units.</li><li>Added <tt>@PreConsumed</tt> to <a shape="rect" href="jpa.html" title="JPA">JPA</a> consumer.</li><li>Added CamelFileName header support to the <a shape="rect" href="hdfs.html" title="HDFS">HDFS</a> producer</li><li>Like as <tt>JpaConsumer</tt> now also <tt>JpaProducer</tt> of the <a shape="rect" href="jpa.html" title="JPA">JPA</a> component supports the <tt>CamelEntityManager</tt> header.</li><li><a shape="rect" href="restlet.html" title="Restlet">Restlet</a> consumer now supports returning custom headers as HTTP headers from the Camel <a shape="rect" href="message.html" title="Message">Message</a>.</l
i><li><a shape="rect" href="spring-java-config.html" title="Spring Java Config">Spring Java Config</a> <tt>CamelConfiguration</tt> now automagically detects all <tt>RouteBuilder</tt> instances registered in the Spring context if <tt>CamelConfiguration#routes</tt> method is not overridden.</li><li>Added support for transferring custom headers with <a shape="rect" href="rabbitmq.html" title="RabbitMQ">RabbitMQ</a> component.</li><li><a shape="rect" href="crypto.html" title="Crypto">PGPDataFormat</a> enables stream cache during unmarshaling.</li><li><tt>FileIdempotentRepository</tt> now creates necessary parent directories together with the new repository file.</li><li><a shape="rect" href="properties.html" title="Properties">Properties</a> component and <a shape="rect" href="using-propertyplaceholder.html" title="Using PropertyPlaceholder">property placeholder</a> will now ignore non existing JVM and environment options as well if <tt>ignoreMissingLocation</tt> is set to <tt>true</tt>
.</li><li>Improved <a shape="rect" href="stream.html" title="Stream">Stream</a> consumer to enrich the <a shape="rect" href="message.html" title="Message">Message</a> with headers about current index / completion flag.</li></ul>
+<ul><li>The MBean names registered by <a shape="rect" href="camel-jmx.html" title="Camel JMX">Camel JMX</a> no longer include the hostname in the <tt>context</tt> part, eg before <tt>context=myHost/myCamelId</tt> and now after <tt>context=myCamelId</tt>. Having the hostname in the MBean name does not bring much value, and in fact makes things more complicated as the mbean name changes depending on the host running Camel.</li><li>When using multiple OSGi Blueprint <cm:property-placeholder>'s then Camel now favors using non-default placeholders, or the last property-placeholder defined in the Blueprint XML file. This allows for example to define default properties in one placeholder, and override these values in other placeholders.</li><li><a shape="rect" href="ftp2.html" title="FTP2">FTP</a> consumer allow to download a single named file without using the FTP LIST command. This allows to download a known file from a FTP server even when the user account does not have permission
to do FTP LIST command.</li><li><a shape="rect" href="ftp2.html" title="FTP2">FTP</a> consumer allow to ignore file not found or insufficient file permission errors.</li><li><a shape="rect" href="data-format.html" title="Data Format">Data Format</a> using marshal now leverages <a shape="rect" href="stream-caching.html" title="Stream caching">Stream caching</a> out of the box if enabled, which allows to marshal big streams and spool to disk, instead of being pure in-memory based.</li><li>Improved using <a shape="rect" href="bean.html" title="Bean">Bean</a> when the bean is looked up in the <a shape="rect" href="registry.html" title="Registry">Registry</a>, when using concurrent processing in the route.</li><li>Added <tt>cache</tt> option to <tt>beanRef</tt> and <tt><bean></tt> in the DSL. This avoids looking up the <a shape="rect" href="bean.html" title="Bean">Bean</a> from the <a shape="rect" href="registry.html" title="Registry">Registry</a> on each usage; this can safely be
done for singleton beans.</li><li>Configuring <a shape="rect" href="data-format.html" title="Data Format">Data Format</a>s in XML attributes now supports reference lookup using the # syntax, eg <tt><jaxb xmlStreamWriterWrapper="#myWriterWrapper" ..></tt></li><li><a shape="rect" href="jdbc.html" title="JDBC">JDBC</a> component now also support <tt>outputType</tt> to specify the expected output as either a List or single Object. As well allow to map to a bean using a <tt>BeanRowMapper</tt> to control the mapping of ROW names to bean properties.</li><li>Both <a shape="rect" href="quartz.html" title="Quartz">Quartz</a> as well as <a shape="rect" href="quartz2.html" title="Quartz2">Quartz2</a> based <a shape="rect" href="scheduledroutepolicy.html" title="ScheduledRoutePolicy">ScheduledRoutePolicy</a> has been improved to better support cluster setups (e.g. to not schedule jobs being already scheduled through another node inside a given cluster).</li><li>Reduced the work the <a sha
pe="rect" href="aggregator2.html" title="Aggregator2">Aggregate</a> EIP does while holding a lock during aggregation, which can lead to improved performance in some use-cases.</li><li><tt>JndiRegistry</tt> now implements all the find methods.</li><li><a shape="rect" href="vm.html" title="VM">VM</a> component now supports <tt>multipleConsumers=true</tt> across deployment units.</li><li>Added <tt>@PreConsumed</tt> to <a shape="rect" href="jpa.html" title="JPA">JPA</a> consumer.</li><li>Added CamelFileName header support to the <a shape="rect" href="hdfs.html" title="HDFS">HDFS</a> producer</li><li>Like as <tt>JpaConsumer</tt> now also <tt>JpaProducer</tt> of the <a shape="rect" href="jpa.html" title="JPA">JPA</a> component supports the <tt>CamelEntityManager</tt> header.</li><li><a shape="rect" href="restlet.html" title="Restlet">Restlet</a> consumer now supports returning custom headers as HTTP headers from the Camel <a shape="rect" href="message.html" title="Message">Message</a>.</l
i><li><a shape="rect" href="spring-java-config.html" title="Spring Java Config">Spring Java Config</a> <tt>CamelConfiguration</tt> now automagically detects all <tt>RouteBuilder</tt> instances registered in the Spring context if <tt>CamelConfiguration#routes</tt> method is not overridden.</li><li>Added support for transferring custom headers with <a shape="rect" href="rabbitmq.html" title="RabbitMQ">RabbitMQ</a> component.</li><li><a shape="rect" href="crypto.html" title="Crypto">PGPDataFormat</a> enables stream cache during unmarshaling.</li><li><tt>FileIdempotentRepository</tt> now creates necessary parent directories together with the new repository file.</li><li><a shape="rect" href="properties.html" title="Properties">Properties</a> component and <a shape="rect" href="using-propertyplaceholder.html" title="Using PropertyPlaceholder">property placeholder</a> will now ignore non existing JVM and environment options as well if <tt>ignoreMissingLocation</tt> is set to <tt>true</tt>
.</li><li>Improved <a shape="rect" href="stream.html" title="Stream">Stream</a> consumer to enrich the <a shape="rect" href="message.html" title="Message">Message</a> with headers about current index / completion flag.</li><li>Added <a shape="rect" href="bean-injection.html" title="Bean Injection"><tt>@BeanInject</tt></a> to inject beans (obtained from the <a shape="rect" href="registry.html" title="Registry">Registry</a>) in your beans such as <tt>RouteBuilder</tt> classes.</li></ul>
<h3><a shape="rect" name="Camel2.13.0Release-FixedIssues"></a>Fixed Issues</h3>
@@ -118,6 +118,9 @@
<h3><a shape="rect" name="Camel2.13.0Release-NewAnnotations"></a>New Annotations</h3>
+<ul><li><a shape="rect" href="bean-injection.html" title="Bean Injection"><tt>@BeanInject</tt></a></li></ul>
+
+
<h3><a shape="rect" name="Camel2.13.0Release-NewDataFormatsDataFormat"></a>New <a shape="rect" href="data-format.html" title="Data Format">Data Formats</a></h3>
<h3><a shape="rect" name="Camel2.13.0Release-NewLanguages"></a>New <a shape="rect" href="languages.html" title="Languages">Languages</a></h3>