Author: buildbot
Date: Wed Aug 3 18:20:41 2016
New Revision: 994388
Log:
Production update by buildbot for camel
Modified:
websites/production/camel/content/book-component-appendix.html
websites/production/camel/content/book-in-one-page.html
websites/production/camel/content/cache/main.pageCache
websites/production/camel/content/jms.html
Modified: websites/production/camel/content/book-component-appendix.html
==============================================================================
--- websites/production/camel/content/book-component-appendix.html (original)
+++ websites/production/camel/content/book-component-appendix.html Wed Aug 3
18:20:41 2016
@@ -1040,11 +1040,11 @@ template.send("direct:alias-verify&
]]></script>
</div></div><p></p><h3 id="BookComponentAppendix-SeeAlso.8">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><ul><li><a
shape="rect" href="crypto.html">Crypto</a> Crypto is also available as a <a
shape="rect" href="data-format.html">Data Format</a></li></ul> <h2
id="BookComponentAppendix-CXFComponent">CXF Component</h2><div
class="confluence-information-macro confluence-information-macro-note"><span
class="aui-icon aui-icon-small aui-iconfont-warning
confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>When using CXF as a consumer, the
<a shape="rect" href="cxf-bean-component.html">CXF Bean Component</a> allows
you to factor out how message payloads are received from their processing as a
RESTful or SOAP web service. This has the potential of using a multitude of
transports to cons
ume web services. The bean component's configuration is also simpler and
provides the fastest method to implement web services using Camel and
CXF.</p></div></div><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>When using CXF in streaming modes
(see DataFormat option), then also read about <a shape="rect"
href="stream-caching.html">Stream caching</a>.</p></div></div><p>The
<strong>cxf:</strong> component provides integration with <a shape="rect"
href="http://cxf.apache.org";>Apache CXF</a> for connecting to JAX-WS services
hosted in CXF.</p><p><style type="text/css">/*<![CDATA[*/
-div.rbtoc1470187065159 {padding: 0px;}
-div.rbtoc1470187065159 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1470187065159 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1470248293499 {padding: 0px;}
+div.rbtoc1470248293499 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1470248293499 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style></p><div class="toc-macro rbtoc1470187065159">
+/*]]>*/</style></p><div class="toc-macro rbtoc1470248293499">
<ul class="toc-indentation"><li><a shape="rect"
href="#BookComponentAppendix-CXFComponent">CXF Component</a>
<ul class="toc-indentation"><li><a shape="rect"
href="#BookComponentAppendix-URIformat">URI format</a></li><li><a shape="rect"
href="#BookComponentAppendix-Options">Options</a>
<ul class="toc-indentation"><li><a shape="rect"
href="#BookComponentAppendix-Thedescriptionsofthedataformats">The descriptions
of the dataformats</a>
@@ -5410,7 +5410,7 @@ rnc:someLocalOrRemoteResource]]></script
</property>
</bean>
]]></script>
-</div></div>Basically, you can configure as many JMS component instances as
you wish giving them each a <strong>unique name using
the</strong> <code>id</code> <strong>attribute</strong>. The preceding
example configures an activemq component. You could do the same to configure
MQSeries, TibCo, BEA, Sonic and so on.<p>Once you have a named JMS component,
you can then refer to endpoints within that component using URIs. For example
for the component name, <code>activemq</code>, you can then refer to
destinations using the URI format,
<code>activemq:[queue:|topic:]destinationName</code>. You can use the same
approach for all other JMS providers.</p><p>This works by the
SpringCamelContext lazily fetching components from the spring context for the
scheme name you use for <a shape="rect" href="endpoint.html">Endpoint</a> <a
shape="rect" href="uris.html">URIs</a> and having the <a shape="rect"
href="component.html">Component</a> resolve the endpoint URIs.</p><h4
id="BookComponentAppen
dix-UsingJNDItofindtheConnectionFactory">Using JNDI to find the
ConnectionFactory</h4><p>If you are using a J2EE container, you might need to
look up JNDI to find the JMS <code>ConnectionFactory</code> rather than use the
usual <code><bean></code> mechanism in Spring. You can do this using
Spring's factory bean or the new Spring XML namespace. For example:</p><div
class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
+</div></div><p> </p><p>Basically, you can configure as many JMS component
instances as you wish giving them each a <strong>unique name using
the</strong> <code>id</code> <strong>attribute</strong>. The preceding
example configures an activemq component. You could do the same to configure
MQSeries, TibCo, BEA, Sonic and so on.</p><p>Once you have a named JMS
component, you can then refer to endpoints within that component using URIs.
For example for the component name, <code>activemq</code>, you can then refer
to destinations using the URI format,
<code>activemq:[queue:|topic:]destinationName</code>. You can use the same
approach for all other JMS providers.</p><p>This works by the
SpringCamelContext lazily fetching components from the spring context for the
scheme name you use for <a shape="rect" href="endpoint.html">Endpoint</a> <a
shape="rect" href="uris.html">URIs</a> and having the <a shape="rect"
href="component.html">Component</a> resolve the endpoint URIs.</p><h4 id
="BookComponentAppendix-UsingJNDItofindtheConnectionFactory">Using JNDI to
find the ConnectionFactory</h4><p>If you are using a J2EE container, you might
need to look up JNDI to find the JMS <code>ConnectionFactory</code> rather than
use the usual <code><bean></code> mechanism in Spring. You can do this
using Spring's factory bean or the new Spring XML namespace. For
example:</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[<bean id="weblogic"
class="org.apache.camel.component.jms.JmsComponent">
<property name="connectionFactory"
ref="myConnectionFactory"/>
</bean>
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 Wed Aug 3 18:20:41
2016
@@ -3619,11 +3619,11 @@ The tutorial has been designed in two pa
While not actual tutorials you might find working through the source of the
various <a shape="rect" href="examples.html">Examples</a> useful.</li></ul>
<h2 id="BookInOnePage-TutorialonSpringRemotingwithJMS">Tutorial on Spring
Remoting with JMS</h2><p> </p><div class="confluence-information-macro
confluence-information-macro-information"><p class="title">Thanks</p><span
class="aui-icon aui-icon-small aui-iconfont-info
confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>This tutorial was kindly donated
to Apache Camel by Martin Gilday.</p></div></div><h2
id="BookInOnePage-Preface">Preface</h2><p>This tutorial aims to guide the
reader through the stages of creating a project which uses Camel to facilitate
the routing of messages from a JMS queue to a <a shape="rect"
class="external-link" href="http://www.springramework.org";
rel="nofollow">Spring</a> service. The route works in a synchronous fashion
returning a response to the client.</p><p><style type="text/css">/*<![CDATA[*/
-div.rbtoc1470187073921 {padding: 0px;}
-div.rbtoc1470187073921 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1470187073921 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1470248322351 {padding: 0px;}
+div.rbtoc1470248322351 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1470248322351 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style></p><div class="toc-macro rbtoc1470187073921">
+/*]]>*/</style></p><div class="toc-macro rbtoc1470248322351">
<ul class="toc-indentation"><li><a shape="rect"
href="#BookInOnePage-TutorialonSpringRemotingwithJMS">Tutorial on Spring
Remoting with JMS</a></li><li><a shape="rect"
href="#BookInOnePage-Preface">Preface</a></li><li><a shape="rect"
href="#BookInOnePage-Prerequisites">Prerequisites</a></li><li><a shape="rect"
href="#BookInOnePage-Distribution">Distribution</a></li><li><a shape="rect"
href="#BookInOnePage-About">About</a></li><li><a shape="rect"
href="#BookInOnePage-CreatetheCamelProject">Create the Camel Project</a>
<ul class="toc-indentation"><li><a shape="rect"
href="#BookInOnePage-UpdatethePOMwithDependencies">Update the POM with
Dependencies</a></li></ul>
</li><li><a shape="rect" href="#BookInOnePage-WritingtheServer">Writing the
Server</a>
@@ -5738,11 +5738,11 @@ So we completed the last piece in the pi
<p>This example has been removed from <strong>Camel 2.9</strong> onwards.
Apache Axis 1.4 is a very old and unsupported framework. We encourage users to
use <a shape="rect" href="cxf.html">CXF</a> instead of Axis.</p></div></div>
<style type="text/css">/*<![CDATA[*/
-div.rbtoc1470187074127 {padding: 0px;}
-div.rbtoc1470187074127 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1470187074127 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1470248323064 {padding: 0px;}
+div.rbtoc1470248323064 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1470248323064 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style><div class="toc-macro rbtoc1470187074127">
+/*]]>*/</style><div class="toc-macro rbtoc1470248323064">
<ul class="toc-indentation"><li><a shape="rect"
href="#BookInOnePage-TutorialusingAxis1.4withApacheCamel">Tutorial using Axis
1.4 with Apache Camel</a>
<ul class="toc-indentation"><li><a shape="rect"
href="#BookInOnePage-Prerequisites">Prerequisites</a></li><li><a shape="rect"
href="#BookInOnePage-Distribution">Distribution</a></li><li><a shape="rect"
href="#BookInOnePage-Introduction">Introduction</a></li><li><a shape="rect"
href="#BookInOnePage-SettinguptheprojecttorunAxis">Setting up the project to
run Axis</a>
<ul class="toc-indentation"><li><a shape="rect"
href="#BookInOnePage-Maven2">Maven 2</a></li><li><a shape="rect"
href="#BookInOnePage-wsdl">wsdl</a></li><li><a shape="rect"
href="#BookInOnePage-ConfiguringAxis">Configuring Axis</a></li><li><a
shape="rect" href="#BookInOnePage-RunningtheExample">Running the
Example</a></li></ul>
@@ -17167,11 +17167,11 @@ template.send("direct:alias-verify&
]]></script>
</div></div><p></p><h3 id="BookInOnePage-SeeAlso.28">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><ul><li><a
shape="rect" href="crypto.html">Crypto</a> Crypto is also available as a <a
shape="rect" href="data-format.html">Data Format</a></li></ul> <h2
id="BookInOnePage-CXFComponent">CXF Component</h2><div
class="confluence-information-macro confluence-information-macro-note"><span
class="aui-icon aui-icon-small aui-iconfont-warning
confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>When using CXF as a consumer, the
<a shape="rect" href="cxf-bean-component.html">CXF Bean Component</a> allows
you to factor out how message payloads are received from their processing as a
RESTful or SOAP web service. This has the potential of using a multitude of
transports to consume web
services. The bean component's configuration is also simpler and provides the
fastest method to implement web services using Camel and
CXF.</p></div></div><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>When using CXF in streaming modes
(see DataFormat option), then also read about <a shape="rect"
href="stream-caching.html">Stream caching</a>.</p></div></div><p>The
<strong>cxf:</strong> component provides integration with <a shape="rect"
href="http://cxf.apache.org";>Apache CXF</a> for connecting to JAX-WS services
hosted in CXF.</p><p><style type="text/css">/*<![CDATA[*/
-div.rbtoc1470187075370 {padding: 0px;}
-div.rbtoc1470187075370 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1470187075370 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1470248352884 {padding: 0px;}
+div.rbtoc1470248352884 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1470248352884 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style></p><div class="toc-macro rbtoc1470187075370">
+/*]]>*/</style></p><div class="toc-macro rbtoc1470248352884">
<ul class="toc-indentation"><li><a shape="rect"
href="#BookInOnePage-CXFComponent">CXF Component</a>
<ul class="toc-indentation"><li><a shape="rect"
href="#BookInOnePage-URIformat">URI format</a></li><li><a shape="rect"
href="#BookInOnePage-Options">Options</a>
<ul class="toc-indentation"><li><a shape="rect"
href="#BookInOnePage-Thedescriptionsofthedataformats">The descriptions of the
dataformats</a>
@@ -21537,7 +21537,7 @@ rnc:someLocalOrRemoteResource]]></script
</property>
</bean>
]]></script>
-</div></div>Basically, you can configure as many JMS component instances as
you wish giving them each a <strong>unique name using
the</strong> <code>id</code> <strong>attribute</strong>. The preceding
example configures an activemq component. You could do the same to configure
MQSeries, TibCo, BEA, Sonic and so on.<p>Once you have a named JMS component,
you can then refer to endpoints within that component using URIs. For example
for the component name, <code>activemq</code>, you can then refer to
destinations using the URI format,
<code>activemq:[queue:|topic:]destinationName</code>. You can use the same
approach for all other JMS providers.</p><p>This works by the
SpringCamelContext lazily fetching components from the spring context for the
scheme name you use for <a shape="rect" href="endpoint.html">Endpoint</a> <a
shape="rect" href="uris.html">URIs</a> and having the <a shape="rect"
href="component.html">Component</a> resolve the endpoint URIs.</p><h4
id="BookInOnePage-Usin
gJNDItofindtheConnectionFactory">Using JNDI to find the
ConnectionFactory</h4><p>If you are using a J2EE container, you might need to
look up JNDI to find the JMS <code>ConnectionFactory</code> rather than use the
usual <code><bean></code> mechanism in Spring. You can do this using
Spring's factory bean or the new Spring XML namespace. For example:</p><div
class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
+</div></div><p> </p><p>Basically, you can configure as many JMS component
instances as you wish giving them each a <strong>unique name using
the</strong> <code>id</code> <strong>attribute</strong>. The preceding
example configures an activemq component. You could do the same to configure
MQSeries, TibCo, BEA, Sonic and so on.</p><p>Once you have a named JMS
component, you can then refer to endpoints within that component using URIs.
For example for the component name, <code>activemq</code>, you can then refer
to destinations using the URI format,
<code>activemq:[queue:|topic:]destinationName</code>. You can use the same
approach for all other JMS providers.</p><p>This works by the
SpringCamelContext lazily fetching components from the spring context for the
scheme name you use for <a shape="rect" href="endpoint.html">Endpoint</a> <a
shape="rect" href="uris.html">URIs</a> and having the <a shape="rect"
href="component.html">Component</a> resolve the endpoint URIs.</p><h4 id
="BookInOnePage-UsingJNDItofindtheConnectionFactory">Using JNDI to find the
ConnectionFactory</h4><p>If you are using a J2EE container, you might need to
look up JNDI to find the JMS <code>ConnectionFactory</code> rather than use the
usual <code><bean></code> mechanism in Spring. You can do this using
Spring's factory bean or the new Spring XML namespace. For example:</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[<bean id="weblogic"
class="org.apache.camel.component.jms.JmsComponent">
<property name="connectionFactory"
ref="myConnectionFactory"/>
</bean>
Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/camel/content/jms.html
==============================================================================
--- websites/production/camel/content/jms.html (original)
+++ websites/production/camel/content/jms.html Wed Aug 3 18:20:41 2016
@@ -154,7 +154,7 @@
</property>
</bean>
]]></script>
-</div></div>Basically, you can configure as many JMS component instances as
you wish giving them each a <strong>unique name using
the</strong> <code>id</code> <strong>attribute</strong>. The preceding
example configures an activemq component. You could do the same to configure
MQSeries, TibCo, BEA, Sonic and so on.<p>Once you have a named JMS component,
you can then refer to endpoints within that component using URIs. For example
for the component name, <code>activemq</code>, you can then refer to
destinations using the URI format,
<code>activemq:[queue:|topic:]destinationName</code>. You can use the same
approach for all other JMS providers.</p><p>This works by the
SpringCamelContext lazily fetching components from the spring context for the
scheme name you use for <a shape="rect" href="endpoint.html">Endpoint</a> <a
shape="rect" href="uris.html">URIs</a> and having the <a shape="rect"
href="component.html">Component</a> resolve the endpoint URIs.</p><h4
id="JMS-UsingJNDItofin
dtheConnectionFactory">Using JNDI to find the ConnectionFactory</h4><p>If you
are using a J2EE container, you might need to look up JNDI to find the JMS
<code>ConnectionFactory</code> rather than use the usual
<code><bean></code> mechanism in Spring. You can do this using Spring's
factory bean or the new Spring XML namespace. For example:</p><div class="code
panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p> </p><p>Basically, you can configure as many JMS component
instances as you wish giving them each a <strong>unique name using
the</strong> <code>id</code> <strong>attribute</strong>. The preceding
example configures an activemq component. You could do the same to configure
MQSeries, TibCo, BEA, Sonic and so on.</p><p>Once you have a named JMS
component, you can then refer to endpoints within that component using URIs.
For example for the component name, <code>activemq</code>, you can then refer
to destinations using the URI format,
<code>activemq:[queue:|topic:]destinationName</code>. You can use the same
approach for all other JMS providers.</p><p>This works by the
SpringCamelContext lazily fetching components from the spring context for the
scheme name you use for <a shape="rect" href="endpoint.html">Endpoint</a> <a
shape="rect" href="uris.html">URIs</a> and having the <a shape="rect"
href="component.html">Component</a> resolve the endpoint URIs.</p><h4 id
="JMS-UsingJNDItofindtheConnectionFactory">Using JNDI to find the
ConnectionFactory</h4><p>If you are using a J2EE container, you might need to
look up JNDI to find the JMS <code>ConnectionFactory</code> rather than use the
usual <code><bean></code> mechanism in Spring. You can do this using
Spring's factory bean or the new Spring XML namespace. For example:</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"><