Author: buildbot
Date: Sun Dec 14 15:19:29 2014
New Revision: 932708
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/jetty.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 Sun Dec 14
15:19:29 2014
@@ -1415,11 +1415,11 @@ template.send("direct:alias-verify&
</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.rbtoc1418296668726 {padding: 0px;}
-div.rbtoc1418296668726 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1418296668726 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1418570301619 {padding: 0px;}
+div.rbtoc1418570301619 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1418570301619 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style></p><div class="toc-macro rbtoc1418296668726">
+/*]]>*/</style></p><div class="toc-macro rbtoc1418570301619">
<ul class="toc-indentation"><li><a shape="rect" href="#CXF-CXFComponent">CXF
Component</a>
<ul class="toc-indentation"><li><a shape="rect" href="#CXF-URIformat">URI
format</a></li><li><a shape="rect" href="#CXF-Options">Options</a>
<ul class="toc-indentation"><li><a shape="rect"
href="#CXF-Thedescriptionsofthedataformats">The descriptions of the
dataformats</a>
@@ -6292,7 +6292,19 @@ X509Certificate cert = (X509Certificate)
</property>
</bean>
]]></script>
-</div></div><h3
id="BookComponentAppendix-DefaultbehaviorforreturningHTTPstatuscodes">Default
behavior for returning HTTP status codes</h3><p>The default behavior of HTTP
status codes is defined by the
<code>org.apache.camel.component.http.DefaultHttpBinding</code> class, which
handles how a response is written and also sets the HTTP status code.</p><p>If
the exchange was processed successfully, the 200 HTTP status code is
returned.<br clear="none"> If the exchange failed with an exception, the 500
HTTP status code is returned, and the stacktrace is returned in the body. If
you want to specify which HTTP status code to return, set the code in the
<code>Exchange.HTTP_RESPONSE_CODE</code> header of the OUT message.</p><h3
id="BookComponentAppendix-CustomizingHttpBinding">Customizing
HttpBinding</h3><p>By default, Camel uses the
<code>org.apache.camel.component.http.DefaultHttpBinding</code> to handle how a
response is written. If you like, you can customize this behavior either by imp
lementing your own <code>HttpBinding</code> class or by extending
<code>DefaultHttpBinding</code> and overriding the appropriate
methods.</p><p>The following example shows how to customize the
<code>DefaultHttpBinding</code> in order to change how exceptions are
returned:</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
+</div></div><h4
id="BookComponentAppendix-ObtainingX-Forwarded-ForheaderwithHttpServletRequest.getRemoteAddr()">Obtaining
X-Forwarded-For header with HttpServletRequest.getRemoteAddr()</h4><p>If the
HTTP requests are handled by an Apache server and forwarded to jetty with
mod_proxy, the original client IP address is in the X-Forwarded-For header and
the HttpServletRequest.getRemoteAddr() will return the address of the Apache
proxy.</p><p>Jetty has a forwarded property which takes the value from
X-Forwarded-For and places it in the HttpServletRequest remoteAddr
property.  This property is not available directly through the endpoint
configuration but it can be easily added using the socketConnectors
property:</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
+<script class="theme: Default; brush: xml; gutter: false"
type="syntaxhighlighter"><![CDATA[<bean id="jetty"
class="org.apache.camel.component.jetty.JettyHttpComponent">
+ <property name="socketConnectors">
+ <map>
+ <entry key="8080">
+ <bean
class="org.eclipse.jetty.server.nio.SelectChannelConnector">
+ <property name="forwarded"
value="true"/>
+ </bean>
+ </entry>
+ </map>
+ </property>
+</bean>]]></script>
+</div></div><p>This is particularly useful when an existing Apache server
handles TLS connections for a domain and proxies them to application servers
internally.</p><h3
id="BookComponentAppendix-DefaultbehaviorforreturningHTTPstatuscodes">Default
behavior for returning HTTP status codes</h3><p>The default behavior of HTTP
status codes is defined by the
<code>org.apache.camel.component.http.DefaultHttpBinding</code> class, which
handles how a response is written and also sets the HTTP status code.</p><p>If
the exchange was processed successfully, the 200 HTTP status code is
returned.<br clear="none"> If the exchange failed with an exception, the 500
HTTP status code is returned, and the stacktrace is returned in the body. If
you want to specify which HTTP status code to return, set the code in the
<code>Exchange.HTTP_RESPONSE_CODE</code> header of the OUT message.</p><h3
id="BookComponentAppendix-CustomizingHttpBinding">Customizing
HttpBinding</h3><p>By default, Camel uses the <code
>org.apache.camel.component.http.DefaultHttpBinding</code> to handle how a
>response is written. If you like, you can customize this behavior either by
>implementing your own <code>HttpBinding</code> class or by extending
><code>DefaultHttpBinding</code> and overriding the appropriate
>methods.</p><p>The following example shows how to customize the
><code>DefaultHttpBinding</code> in order to change how exceptions are
>returned:</p><div class="code panel pdl" style="border-width: 1px;"><div
>class="codeContent panelContent pdl">
<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
public class MyHttpBinding extends DefaultHttpBinding {
public MyHttpBinding(HttpEndpoint ep) {
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 Sun Dec 14 15:19:29
2014
@@ -4126,11 +4126,11 @@ While not actual tutorials you might fin
</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.rbtoc1418393862185 {padding: 0px;}
-div.rbtoc1418393862185 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1418393862185 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1418570308079 {padding: 0px;}
+div.rbtoc1418570308079 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1418570308079 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style></p><div class="toc-macro rbtoc1418393862185">
+/*]]>*/</style></p><div class="toc-macro rbtoc1418570308079">
<ul class="toc-indentation"><li><a shape="rect"
href="#Tutorial-JmsRemoting-TutorialonSpringRemotingwithJMS">Tutorial on Spring
Remoting with JMS</a></li><li><a shape="rect"
href="#Tutorial-JmsRemoting-Preface">Preface</a></li><li><a shape="rect"
href="#Tutorial-JmsRemoting-Prerequisites">Prerequisites</a></li><li><a
shape="rect"
href="#Tutorial-JmsRemoting-Distribution">Distribution</a></li><li><a
shape="rect" href="#Tutorial-JmsRemoting-About">About</a></li><li><a
shape="rect" href="#Tutorial-JmsRemoting-CreatetheCamelProject">Create the
Camel Project</a>
<ul class="toc-indentation"><li><a shape="rect"
href="#Tutorial-JmsRemoting-UpdatethePOMwithDependencies">Update the POM with
Dependencies</a></li></ul>
</li><li><a shape="rect" href="#Tutorial-JmsRemoting-WritingtheServer">Writing
the Server</a>
@@ -6316,11 +6316,11 @@ So we completed the last piece in the pi
<style type="text/css">/*<![CDATA[*/
-div.rbtoc1418393863657 {padding: 0px;}
-div.rbtoc1418393863657 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1418393863657 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1418570308323 {padding: 0px;}
+div.rbtoc1418570308323 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1418570308323 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style><div class="toc-macro rbtoc1418393863657">
+/*]]>*/</style><div class="toc-macro rbtoc1418570308323">
<ul class="toc-indentation"><li><a shape="rect"
href="#Tutorial-AXIS-Camel-TutorialusingAxis1.4withApacheCamel">Tutorial using
Axis 1.4 with Apache Camel</a>
<ul class="toc-indentation"><li><a shape="rect"
href="#Tutorial-AXIS-Camel-Prerequisites">Prerequisites</a></li><li><a
shape="rect"
href="#Tutorial-AXIS-Camel-Distribution">Distribution</a></li><li><a
shape="rect"
href="#Tutorial-AXIS-Camel-Introduction">Introduction</a></li><li><a
shape="rect" href="#Tutorial-AXIS-Camel-SettinguptheprojecttorunAxis">Setting
up the project to run Axis</a>
<ul class="toc-indentation"><li><a shape="rect"
href="#Tutorial-AXIS-Camel-Maven2">Maven 2</a></li><li><a shape="rect"
href="#Tutorial-AXIS-Camel-wsdl">wsdl</a></li><li><a shape="rect"
href="#Tutorial-AXIS-Camel-ConfiguringAxis">Configuring Axis</a></li><li><a
shape="rect" href="#Tutorial-AXIS-Camel-RunningtheExample">Running the
Example</a></li></ul>
@@ -19229,11 +19229,11 @@ template.send("direct:alias-verify&
</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.rbtoc1418393885717 {padding: 0px;}
-div.rbtoc1418393885717 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1418393885717 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1418570313593 {padding: 0px;}
+div.rbtoc1418570313593 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1418570313593 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style></p><div class="toc-macro rbtoc1418393885717">
+/*]]>*/</style></p><div class="toc-macro rbtoc1418570313593">
<ul class="toc-indentation"><li><a shape="rect" href="#CXF-CXFComponent">CXF
Component</a>
<ul class="toc-indentation"><li><a shape="rect" href="#CXF-URIformat">URI
format</a></li><li><a shape="rect" href="#CXF-Options">Options</a>
<ul class="toc-indentation"><li><a shape="rect"
href="#CXF-Thedescriptionsofthedataformats">The descriptions of the
dataformats</a>
@@ -24106,7 +24106,19 @@ X509Certificate cert = (X509Certificate)
</property>
</bean>
]]></script>
-</div></div><h3
id="BookInOnePage-DefaultbehaviorforreturningHTTPstatuscodes">Default behavior
for returning HTTP status codes</h3><p>The default behavior of HTTP status
codes is defined by the
<code>org.apache.camel.component.http.DefaultHttpBinding</code> class, which
handles how a response is written and also sets the HTTP status code.</p><p>If
the exchange was processed successfully, the 200 HTTP status code is
returned.<br clear="none"> If the exchange failed with an exception, the 500
HTTP status code is returned, and the stacktrace is returned in the body. If
you want to specify which HTTP status code to return, set the code in the
<code>Exchange.HTTP_RESPONSE_CODE</code> header of the OUT message.</p><h3
id="BookInOnePage-CustomizingHttpBinding">Customizing HttpBinding</h3><p>By
default, Camel uses the
<code>org.apache.camel.component.http.DefaultHttpBinding</code> to handle how a
response is written. If you like, you can customize this behavior either by
implementing your o
wn <code>HttpBinding</code> class or by extending
<code>DefaultHttpBinding</code> and overriding the appropriate
methods.</p><p>The following example shows how to customize the
<code>DefaultHttpBinding</code> in order to change how exceptions are
returned:</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
+</div></div><h4
id="BookInOnePage-ObtainingX-Forwarded-ForheaderwithHttpServletRequest.getRemoteAddr()">Obtaining
X-Forwarded-For header with HttpServletRequest.getRemoteAddr()</h4><p>If the
HTTP requests are handled by an Apache server and forwarded to jetty with
mod_proxy, the original client IP address is in the X-Forwarded-For header and
the HttpServletRequest.getRemoteAddr() will return the address of the Apache
proxy.</p><p>Jetty has a forwarded property which takes the value from
X-Forwarded-For and places it in the HttpServletRequest remoteAddr
property.  This property is not available directly through the endpoint
configuration but it can be easily added using the socketConnectors
property:</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
+<script class="theme: Default; brush: xml; gutter: false"
type="syntaxhighlighter"><![CDATA[<bean id="jetty"
class="org.apache.camel.component.jetty.JettyHttpComponent">
+ <property name="socketConnectors">
+ <map>
+ <entry key="8080">
+ <bean
class="org.eclipse.jetty.server.nio.SelectChannelConnector">
+ <property name="forwarded"
value="true"/>
+ </bean>
+ </entry>
+ </map>
+ </property>
+</bean>]]></script>
+</div></div><p>This is particularly useful when an existing Apache server
handles TLS connections for a domain and proxies them to application servers
internally.</p><h3
id="BookInOnePage-DefaultbehaviorforreturningHTTPstatuscodes">Default behavior
for returning HTTP status codes</h3><p>The default behavior of HTTP status
codes is defined by the
<code>org.apache.camel.component.http.DefaultHttpBinding</code> class, which
handles how a response is written and also sets the HTTP status code.</p><p>If
the exchange was processed successfully, the 200 HTTP status code is
returned.<br clear="none"> If the exchange failed with an exception, the 500
HTTP status code is returned, and the stacktrace is returned in the body. If
you want to specify which HTTP status code to return, set the code in the
<code>Exchange.HTTP_RESPONSE_CODE</code> header of the OUT message.</p><h3
id="BookInOnePage-CustomizingHttpBinding">Customizing HttpBinding</h3><p>By
default, Camel uses the <code>org.apache.came
l.component.http.DefaultHttpBinding</code> to handle how a response is
written. If you like, you can customize this behavior either by implementing
your own <code>HttpBinding</code> class or by extending
<code>DefaultHttpBinding</code> and overriding the appropriate
methods.</p><p>The following example shows how to customize the
<code>DefaultHttpBinding</code> in order to change how exceptions are
returned:</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
public class MyHttpBinding extends DefaultHttpBinding {
public MyHttpBinding(HttpEndpoint ep) {
Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/camel/content/jetty.html
==============================================================================
--- websites/production/camel/content/jetty.html (original)
+++ websites/production/camel/content/jetty.html Sun Dec 14 15:19:29 2014
@@ -277,7 +277,19 @@ X509Certificate cert = (X509Certificate)
</property>
</bean>
]]></script>
-</div></div><h3 id="Jetty-DefaultbehaviorforreturningHTTPstatuscodes">Default
behavior for returning HTTP status codes</h3><p>The default behavior of HTTP
status codes is defined by the
<code>org.apache.camel.component.http.DefaultHttpBinding</code> class, which
handles how a response is written and also sets the HTTP status code.</p><p>If
the exchange was processed successfully, the 200 HTTP status code is
returned.<br clear="none"> If the exchange failed with an exception, the 500
HTTP status code is returned, and the stacktrace is returned in the body. If
you want to specify which HTTP status code to return, set the code in the
<code>Exchange.HTTP_RESPONSE_CODE</code> header of the OUT message.</p><h3
id="Jetty-CustomizingHttpBinding">Customizing HttpBinding</h3><p>By default,
Camel uses the <code>org.apache.camel.component.http.DefaultHttpBinding</code>
to handle how a response is written. If you like, you can customize this
behavior either by implementing your own <code>HttpBin
ding</code> class or by extending <code>DefaultHttpBinding</code> and
overriding the appropriate methods.</p><p>The following example shows how to
customize the <code>DefaultHttpBinding</code> in order to change how exceptions
are returned:</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
+</div></div><h4
id="Jetty-ObtainingX-Forwarded-ForheaderwithHttpServletRequest.getRemoteAddr()">Obtaining
X-Forwarded-For header with HttpServletRequest.getRemoteAddr()</h4><p>If the
HTTP requests are handled by an Apache server and forwarded to jetty with
mod_proxy, the original client IP address is in the X-Forwarded-For header and
the HttpServletRequest.getRemoteAddr() will return the address of the Apache
proxy.</p><p>Jetty has a forwarded property which takes the value from
X-Forwarded-For and places it in the HttpServletRequest remoteAddr
property.  This property is not available directly through the endpoint
configuration but it can be easily added using the socketConnectors
property:</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
+<script class="theme: Default; brush: xml; gutter: false"
type="syntaxhighlighter"><![CDATA[<bean id="jetty"
class="org.apache.camel.component.jetty.JettyHttpComponent">
+ <property name="socketConnectors">
+ <map>
+ <entry key="8080">
+ <bean
class="org.eclipse.jetty.server.nio.SelectChannelConnector">
+ <property name="forwarded"
value="true"/>
+ </bean>
+ </entry>
+ </map>
+ </property>
+</bean>]]></script>
+</div></div><p>This is particularly useful when an existing Apache server
handles TLS connections for a domain and proxies them to application servers
internally.</p><h3
id="Jetty-DefaultbehaviorforreturningHTTPstatuscodes">Default behavior for
returning HTTP status codes</h3><p>The default behavior of HTTP status codes is
defined by the <code>org.apache.camel.component.http.DefaultHttpBinding</code>
class, which handles how a response is written and also sets the HTTP status
code.</p><p>If the exchange was processed successfully, the 200 HTTP status
code is returned.<br clear="none"> If the exchange failed with an exception,
the 500 HTTP status code is returned, and the stacktrace is returned in the
body. If you want to specify which HTTP status code to return, set the code in
the <code>Exchange.HTTP_RESPONSE_CODE</code> header of the OUT message.</p><h3
id="Jetty-CustomizingHttpBinding">Customizing HttpBinding</h3><p>By default,
Camel uses the <code>org.apache.camel.component.http
.DefaultHttpBinding</code> to handle how a response is written. If you like,
you can customize this behavior either by implementing your own
<code>HttpBinding</code> class or by extending <code>DefaultHttpBinding</code>
and overriding the appropriate methods.</p><p>The following example shows how
to customize the <code>DefaultHttpBinding</code> in order to change how
exceptions are returned:</p><div class="code panel pdl" style="border-width:
1px;"><div class="codeContent panelContent pdl">
<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><