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 2014/02/18 08:21:05 UTC
svn commit: r898366 [6/8] - in /websites/production/camel/content: ./ cache/
Modified: websites/production/camel/content/http4.html
==============================================================================
--- websites/production/camel/content/http4.html (original)
+++ websites/production/camel/content/http4.html Tue Feb 18 07:21:04 2014
@@ -41,7 +41,6 @@
<script src='//camel.apache.org/styles/highlighter/scripts/shCore.js' type='text/javascript'></script>
<script src='//camel.apache.org/styles/highlighter/scripts/shBrushJava.js' type='text/javascript'></script>
<script src='//camel.apache.org/styles/highlighter/scripts/shBrushXml.js' type='text/javascript'></script>
- <script src='//camel.apache.org/styles/highlighter/scripts/shBrushPlain.js' type='text/javascript'></script>
<script type="text/javascript">
SyntaxHighlighter.defaults['toolbar'] = false;
@@ -111,11 +110,11 @@
<p>You can only produce to endpoints generated by the HTTP4 component. Therefore it should never be used as input into your Camel Routes. To bind/expose an HTTP endpoint via a HTTP server as input to a Camel route, use the <a shape="rect" href="jetty.html">Jetty Component</a> instead.</p>
</div>
</div>
-<h3 id="HTTP4-HttpComponentOptions">HttpComponent Options</h3><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Default Value </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>maxTotalConnections</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>200</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The maximum number of connections. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>connectionsPerRoute</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>20</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The maximum number of connections per route. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>cookieStore</code> </p></td><td colspan
="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.11.2/2.12.0:</strong> To use a custom <code>org.apache.http.client.CookieStore</code>. By default the <code>org.apache.http.impl.client.BasicCookieStore</code> is used which is an in-memory only cookie store. Notice if <code>bridgeEndpoint=true</code> then the cookie store is forced to be a noop cookie store as cookies shouldn't be stored as we are just bridging (eg acting as a proxy). </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>httpClientConfigurer</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Reference to a <code>org.apache.camel.component.http.HttpClientConfigurer</code> in the <a shape="rect" href="registry.html" title="Registry">Registry</a>. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<p> <code>clientConnectionManager</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> To use a custom <code>org.apache.http.conn.ClientConnectionManager</code>. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>httpBinding</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> To use a custom <code>org.apache.camel.component.http.HttpBinding</code>. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>httpContext</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.9.2:</strong> To use a custom <code>org.apache.http.protocol.HttpContext</code> when executing requests. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><
p> <code>sslContextParameters</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.8:</strong> To use a custom <code>org.apache.camel.util.jsse.SSLContextParameters</code>. See <a shape="rect" href="#HTTP4-UsingtheJSSEConfigurationUtility">Using the JSSE Configuration Utility</a>. <strong>Important:</strong> Only one instance of <code>org.apache.camel.util.jsse.SSLContextParameters</code> is supported per HttpComponent. If you need to use 2 or more different instances, you need to define a new HttpComponent per instance you need. See further below for more details. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>x509HostnameVerifier</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>BrowserCompatHostnameVerifier</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.7:</strong> You can refer
to a different <code>org.apache.http.conn.ssl.X509HostnameVerifier</code> instance in the <a shape="rect" href="registry.html" title="Registry">Registry</a> such as <code>org.apache.http.conn.ssl.StrictHostnameVerifier</code> or <code>org.apache.http.conn.ssl.AllowAllHostnameVerifier</code>. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>connectionTimeToLive</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>-1</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.11.0:</strong> The time for connection to live, the time unit is millisecond, the default value is always keep alive. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>authenticationPreemptive</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>false</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.11.3/2.12.2:</strong> If this option is true, camel-http
4 sends preemptive basic authentication to the server. </p></td></tr></tbody></table>
-<h3 id="HTTP4-HttpEndpointOptions">HttpEndpoint Options</h3><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Default Value </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>throwExceptionOnFailure</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>true</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Option to disable throwing the <code>HttpOperationFailedException</code> in case of failed responses from the remote server. This allows you to get all responses regardless of the HTTP status code. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>bridgeEndpoint</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>false</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><
p> If true, HttpProducer will ignore the Exchange.HTTP_URI header, and use the endpoint's URI for request. You may also set the <strong>throwExcpetionOnFailure</strong> to be false to let the HttpProducer send all fault responses back. Also if set to true HttpProducer and CamelServlet will skip the gzip processing if the content-encoding is "gzip". </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>clearExpiredCookies</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>true</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.11.2/2.12.0:</strong> Whether to clear expired cookies before sending the HTTP request. This ensures the cookies store does not keep growing by adding new cookies which is newer removed when they are expired. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>cookieStore</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code>
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.11.2/2.12.0:</strong> To use a custom <code>org.apache.http.client.CookieStore</code>. By default the <code>org.apache.http.impl.client.BasicCookieStore</code> is used which is an in-memory only cookie store. Notice if <code>bridgeEndpoint=true</code> then the cookie store is forced to be a noop cookie store as cookies shouldn't be stored as we are just bridging (eg acting as a proxy). </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>disableStreamCache</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>false</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> DefaultHttpBinding will copy the request input stream into a stream cache and put it into the message body if this option is false to support multiple reads, otherwise DefaultHttpBinding will set the request input stream directly in the message body. </p></td></tr><tr><td colspan="1
" rowspan="1" class="confluenceTd"><p> <code>headerFilterStrategy</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.10.4:</strong> Reference to a instance of <code>org.apache.camel.spi.HeaderFilterStrategy</code> in the <a shape="rect" href="registry.html" title="Registry">Registry</a>. It will be used to apply the custom headerFilterStrategy on the new create HttpEndpoint. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>httpBindingRef</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Deprecated and will be removed in Camel 3.0:</strong> Reference to a <code>org.apache.camel.component.http.HttpBinding</code> in the <a shape="rect" href="registry.html" title="Registry">Registry</a>. Use the <code>httpBinding</code> option instead. <
/p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>httpBinding</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> To use a custom <code>org.apache.camel.component.http.HttpBinding</code>. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>httpClientConfigurerRef</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Deprecated and will be removed in Camel 3.0:</strong> Reference to a <code>org.apache.camel.component.http.HttpClientConfigurer</code> in the <a shape="rect" href="registry.html" title="Registry">Registry</a>. Use the <code>httpClientConfigurer</code> option instead. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>httpClientConfigurer</code> </p></td><td colspan="1" rowspan="1" class="confluenceT
d"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Reference to a <code>org.apache.camel.component.http.HttpClientConfigurer</code> in the <a shape="rect" href="registry.html" title="Registry">Registry</a>. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>httpContextRef</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Deprecated and will be removed in Camel 3.0:</strong> <strong>Camel 2.9.2:</strong> Reference to a custom <code>org.apache.http.protocol.HttpContext</code> in the <a shape="rect" href="registry.html" title="Registry">Registry</a>. Use the <code>httpContext</code> option instead. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>httpContext</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confl
uenceTd"><p> <strong>Camel 2.9.2:</strong> To use a custom <code>org.apache.http.protocol.HttpContext</code> when executing requests. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>httpClient.XXX</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Setting options on the <a shape="rect" class="external-link" href="http://hc.apache.org/httpcomponents-core-ga/httpcore/apidocs/org/apache/http/params/BasicHttpParams.html">BasicHttpParams</a>. For instance <code>httpClient.soTimeout=5000</code> will set the <code>SO_TIMEOUT</code> to 5 seconds. Look on the setter methods of the following parameter beans for a complete reference: <a shape="rect" class="external-link" href="http://hc.apache.org/httpcomponents-client-ga/httpclient/apidocs/org/apache/http/auth/params/AuthParamBean.html">AuthParamBean</a>, <a shape="rect" class="external-link" href="http://hc.apache.or
g/httpcomponents-client-ga/httpclient/apidocs/org/apache/http/client/params/ClientParamBean.html">ClientParamBean</a>, <a shape="rect" class="external-link" href="http://hc.apache.org/httpcomponents-client-ga/httpclient/apidocs/org/apache/http/conn/params/ConnConnectionParamBean.html">ConnConnectionParamBean</a>, <a shape="rect" class="external-link" href="http://hc.apache.org/httpcomponents-client-ga/httpclient/apidocs/org/apache/http/conn/params/ConnRouteParamBean.html">ConnRouteParamBean</a>, <a shape="rect" class="external-link" href="http://hc.apache.org/httpcomponents-client-ga/httpclient/apidocs/org/apache/http/cookie/params/CookieSpecParamBean.html">CookieSpecParamBean</a>, <a shape="rect" class="external-link" href="http://hc.apache.org/httpcomponents-core-ga/httpcore/apidocs/org/apache/http/params/HttpConnectionParamBean.html">HttpConnectionParamBean</a> and <a shape="rect" class="external-link" href="http://hc.apache.org/httpcomponents-core-ga/httpcore/apidocs/org/apache/
http/params/HttpProtocolParamBean.html">HttpProtocolParamBean</a> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>clientConnectionManager</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> To use a custom <code>org.apache.http.conn.ClientConnectionManager</code>. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>transferException</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>false</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> If enabled and an <a shape="rect" href="exchange.html" title="Exchange">Exchange</a> failed processing on the consumer side, and if the caused <code>Exception</code> was send back serialized in the response as a <code>application/x-java-serialized-object</code> content type (for example using <a shape="rect" href="jetty.html" title="Jetty">Jetty</a> or <a sha
pe="rect" href="servlet.html" title="SERVLET">SERVLET</a> Camel components). On the producer side the exception will be deserialized and thrown as is, instead of the <code>HttpOperationFailedException</code>. The caused exception is required to be serialized. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>sslContextParametersRef</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Deprecated and will be removed in Camel 3.0:</strong> <strong>Camel 2.8:</strong> Reference to a <code>org.apache.camel.util.jsse.SSLContextParameters</code> in the <a shape="rect" href="registry.html" title="Registry">Registry</a>. <strong>Important:</strong> Only one instance of <code>org.apache.camel.util.jsse.SSLContextParameters</code> is supported per HttpComponent. If you need to use 2 or more different instances, you need to define a new HttpComponent per instance y
ou need. See further below for more details. See <a shape="rect" href="#HTTP4-UsingtheJSSEConfigurationUtility">Using the JSSE Configuration Utility</a>. Use the <code>sslContextParameters</code> option instead. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>sslContextParameters</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.11.1:</strong> Reference to a <code>org.apache.camel.util.jsse.SSLContextParameters</code> in the <a shape="rect" href="registry.html" title="Registry">Registry</a>. <strong>Important:</strong> Only one instance of <code>org.apache.camel.util.jsse.SSLContextParameters</code> is supported per HttpComponent. If you need to use 2 or more different instances, you need to define a new HttpComponent per instance you need. See further below for more details. See <a shape="rect" href="#HTTP4-UsingtheJSSEConfigurationUtility
">Using the JSSE Configuration Utility</a>. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>x509HostnameVerifier</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>BrowserCompatHostnameVerifier</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.7:</strong> You can refer to a different <code>org.apache.http.conn.ssl.X509HostnameVerifier</code> instance in the <a shape="rect" href="registry.html" title="Registry">Registry</a> such as <code>org.apache.http.conn.ssl.StrictHostnameVerifier</code> or <code>org.apache.http.conn.ssl.AllowAllHostnameVerifier</code>. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>urlRewrite</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.11:</strong> <strong>Producer only</strong> Refers to a custom <code>org.apache.camel.compone
nt.http4.UrlRewrite</code> which allows you to rewrite urls when you bridge/proxy endpoints. See more details at <a shape="rect" href="urlrewrite.html" title="UrlRewrite">UrlRewrite</a> and <a shape="rect" href="how-to-use-camel-as-a-http-proxy-between-a-client-and-server.html" title="How to use Camel as a HTTP proxy between a client and server">How to use Camel as a HTTP proxy between a client and server</a>. </p></td></tr></tbody></table>
-<p>The following authentication options can also be set on the HttpEndpoint:</p><h4 id="HTTP4-SettingBasicAuthenticationandProxy">Setting Basic Authentication and Proxy</h4><p><strong>Before Camel 2.8.0</strong></p><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Default Value </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>username</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Username for authentication. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>password</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Password for authentication. </p>
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>domain</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The domain name for authentication. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>host</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The host name authentication. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>proxyHost</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The proxy host name </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>proxyPort</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" clas
s="confluenceTd"><p> The proxy port number </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>proxyUsername</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Username for proxy authentication </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>proxyPassword</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Password for proxy authentication </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>proxyDomain</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The proxy domain name </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>proxyNtHost</code> </p></td><td colspan="1" rowspan="1" class="conflu
enceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The proxy Nt host name </p></td></tr></tbody></table>
-<p><strong>Since Camel 2.8.0</strong></p><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Default Value </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>authUsername</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Username for authentication </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>authPassword</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Password for authentication </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>authDomain</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</cod
e> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The domain name for authentication </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>authHost</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The host name authentication </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>proxyAuthHost</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The proxy host name </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>proxyAuthPort</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The proxy port number </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>proxyAuthScheme</code> </p></td><t
d colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The proxy scheme, will fallback and use the scheme from the endpoint if not configured. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>proxyAuthUsername</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Username for proxy authentication </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>proxyAuthPassword</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Password for proxy authentication </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>proxyAuthDomain</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class
="confluenceTd"><p> The proxy domain name </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>proxyAuthNtHost</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The proxy Nt host name </p></td></tr></tbody></table>
-<h3 id="HTTP4-MessageHeaders">Message Headers</h3><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>Exchange.HTTP_URI</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>String</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> URI to call. Will override existing URI set directly on the endpoint. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>Exchange.HTTP_PATH</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>String</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Request URI's path, the header will be used to build the request URI with the HTTP_URI. </p></td></tr><tr><td colspan="1" rowspan="1" class="co
nfluenceTd"><p> <code>Exchange.HTTP_QUERY</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>String</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> URI parameters. Will override existing URI parameters set directly on the endpoint. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>Exchange.HTTP_RESPONSE_CODE</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>int</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The HTTP response code from the external server. Is 200 for OK. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>Exchange.HTTP_CHARACTER_ENCODING</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>String</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Character encoding. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>Exchange.CONTENT_TYPE</code> </p></td><td col
span="1" rowspan="1" class="confluenceTd"><p> <code>String</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The HTTP content type. Is set on both the IN and OUT message to provide a content type, such as <code>text/html</code>. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>Exchange.CONTENT_ENCODING</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>String</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The HTTP content encoding. Is set on both the IN and OUT message to provide a content encoding, such as <code>gzip</code>. </p></td></tr></tbody></table>
+<h3 id="HTTP4-HttpComponentOptions">HttpComponent Options</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Default Value </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>maxTotalConnections</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>200</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The maximum number of connections. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>connectionsPerRoute</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>20</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The maximum number of connections per route. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>cookieStore</co
de> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.11.2/2.12.0:</strong> To use a custom <code>org.apache.http.client.CookieStore</code>. By default the <code>org.apache.http.impl.client.BasicCookieStore</code> is used which is an in-memory only cookie store. Notice if <code>bridgeEndpoint=true</code> then the cookie store is forced to be a noop cookie store as cookies shouldn't be stored as we are just bridging (eg acting as a proxy). </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>httpClientConfigurer</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Reference to a <code>org.apache.camel.component.http.HttpClientConfigurer</code> in the <a shape="rect" href="registry.html">Registry</a>. </p></td></tr><tr><td colspan="1" rowspan="1" class="conflue
nceTd"><p> <code>clientConnectionManager</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> To use a custom <code>org.apache.http.conn.ClientConnectionManager</code>. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>httpBinding</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> To use a custom <code>org.apache.camel.component.http.HttpBinding</code>. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>httpContext</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.9.2:</strong> To use a custom <code>org.apache.http.protocol.HttpContext</code> when executing requests. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluen
ceTd"><p> <code>sslContextParameters</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.8:</strong> To use a custom <code>org.apache.camel.util.jsse.SSLContextParameters</code>. See <a shape="rect" href="#HTTP4-UsingtheJSSEConfigurationUtility">Using the JSSE Configuration Utility</a>. <strong>Important:</strong> Only one instance of <code>org.apache.camel.util.jsse.SSLContextParameters</code> is supported per HttpComponent. If you need to use 2 or more different instances, you need to define a new HttpComponent per instance you need. See further below for more details. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>x509HostnameVerifier</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>BrowserCompatHostnameVerifier</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.7:</strong> You ca
n refer to a different <code>org.apache.http.conn.ssl.X509HostnameVerifier</code> instance in the <a shape="rect" href="registry.html">Registry</a> such as <code>org.apache.http.conn.ssl.StrictHostnameVerifier</code> or <code>org.apache.http.conn.ssl.AllowAllHostnameVerifier</code>. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>connectionTimeToLive</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>-1</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.11.0:</strong> The time for connection to live, the time unit is millisecond, the default value is always keep alive. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>authenticationPreemptive</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>false</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.11.3/2.12.2:</strong> If this option is true, camel-http4 sends pr
eemptive basic authentication to the server. </p></td></tr></tbody></table></div>
+<h3 id="HTTP4-HttpEndpointOptions">HttpEndpoint Options</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Default Value </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>throwExceptionOnFailure</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>true</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Option to disable throwing the <code>HttpOperationFailedException</code> in case of failed responses from the remote server. This allows you to get all responses regardless of the HTTP status code. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>bridgeEndpoint</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>false</code> </p></td><td colspan="1" rowspan="1
" class="confluenceTd"><p> If true, HttpProducer will ignore the Exchange.HTTP_URI header, and use the endpoint's URI for request. You may also set the <strong>throwExcpetionOnFailure</strong> to be false to let the HttpProducer send all fault responses back. Also if set to true HttpProducer and CamelServlet will skip the gzip processing if the content-encoding is "gzip". </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>clearExpiredCookies</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>true</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.11.2/2.12.0:</strong> Whether to clear expired cookies before sending the HTTP request. This ensures the cookies store does not keep growing by adding new cookies which is newer removed when they are expired. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>cookieStore</code> </p></td><td colspan="1" rowspan="1" class="confluenceT
d"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.11.2/2.12.0:</strong> To use a custom <code>org.apache.http.client.CookieStore</code>. By default the <code>org.apache.http.impl.client.BasicCookieStore</code> is used which is an in-memory only cookie store. Notice if <code>bridgeEndpoint=true</code> then the cookie store is forced to be a noop cookie store as cookies shouldn't be stored as we are just bridging (eg acting as a proxy). </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>disableStreamCache</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>false</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> DefaultHttpBinding will copy the request input stream into a stream cache and put it into the message body if this option is false to support multiple reads, otherwise DefaultHttpBinding will set the request input stream directly in the message body. </p></td
></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>headerFilterStrategy</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.10.4:</strong> Reference to a instance of <code>org.apache.camel.spi.HeaderFilterStrategy</code> in the <a shape="rect" href="registry.html">Registry</a>. It will be used to apply the custom headerFilterStrategy on the new create HttpEndpoint. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>httpBindingRef</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Deprecated and will be removed in Camel 3.0:</strong> Reference to a <code>org.apache.camel.component.http.HttpBinding</code> in the <a shape="rect" href="registry.html">Registry</a>. Use the <code>httpBinding</code> option instead. </p></td></
tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>httpBinding</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> To use a custom <code>org.apache.camel.component.http.HttpBinding</code>. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>httpClientConfigurerRef</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Deprecated and will be removed in Camel 3.0:</strong> Reference to a <code>org.apache.camel.component.http.HttpClientConfigurer</code> in the <a shape="rect" href="registry.html">Registry</a>. Use the <code>httpClientConfigurer</code> option instead. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>httpClientConfigurer</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </
p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Reference to a <code>org.apache.camel.component.http.HttpClientConfigurer</code> in the <a shape="rect" href="registry.html">Registry</a>. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>httpContextRef</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Deprecated and will be removed in Camel 3.0:</strong> <strong>Camel 2.9.2:</strong> Reference to a custom <code>org.apache.http.protocol.HttpContext</code> in the <a shape="rect" href="registry.html">Registry</a>. Use the <code>httpContext</code> option instead. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>httpContext</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.9.2:</strong> To use a custom <c
ode>org.apache.http.protocol.HttpContext</code> when executing requests. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>httpClient.XXX</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Setting options on the <a shape="rect" class="external-link" href="http://hc.apache.org/httpcomponents-core-ga/httpcore/apidocs/org/apache/http/params/BasicHttpParams.html">BasicHttpParams</a>. For instance <code>httpClient.soTimeout=5000</code> will set the <code>SO_TIMEOUT</code> to 5 seconds. Look on the setter methods of the following parameter beans for a complete reference: <a shape="rect" class="external-link" href="http://hc.apache.org/httpcomponents-client-ga/httpclient/apidocs/org/apache/http/auth/params/AuthParamBean.html">AuthParamBean</a>, <a shape="rect" class="external-link" href="http://hc.apache.org/httpcomponents-client-ga/httpclient/apidocs/org/apache/http
/client/params/ClientParamBean.html">ClientParamBean</a>, <a shape="rect" class="external-link" href="http://hc.apache.org/httpcomponents-client-ga/httpclient/apidocs/org/apache/http/conn/params/ConnConnectionParamBean.html">ConnConnectionParamBean</a>, <a shape="rect" class="external-link" href="http://hc.apache.org/httpcomponents-client-ga/httpclient/apidocs/org/apache/http/conn/params/ConnRouteParamBean.html">ConnRouteParamBean</a>, <a shape="rect" class="external-link" href="http://hc.apache.org/httpcomponents-client-ga/httpclient/apidocs/org/apache/http/cookie/params/CookieSpecParamBean.html">CookieSpecParamBean</a>, <a shape="rect" class="external-link" href="http://hc.apache.org/httpcomponents-core-ga/httpcore/apidocs/org/apache/http/params/HttpConnectionParamBean.html">HttpConnectionParamBean</a> and <a shape="rect" class="external-link" href="http://hc.apache.org/httpcomponents-core-ga/httpcore/apidocs/org/apache/http/params/HttpProtocolParamBean.html">HttpProtocolParamBean
</a> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>clientConnectionManager</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> To use a custom <code>org.apache.http.conn.ClientConnectionManager</code>. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>transferException</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>false</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> If enabled and an <a shape="rect" href="exchange.html">Exchange</a> failed processing on the consumer side, and if the caused <code>Exception</code> was send back serialized in the response as a <code>application/x-java-serialized-object</code> content type (for example using <a shape="rect" href="jetty.html">Jetty</a> or <a shape="rect" href="servlet.html">Servlet</a> Camel components). On the producer side the except
ion will be deserialized and thrown as is, instead of the <code>HttpOperationFailedException</code>. The caused exception is required to be serialized. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>sslContextParametersRef</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Deprecated and will be removed in Camel 3.0:</strong> <strong>Camel 2.8:</strong> Reference to a <code>org.apache.camel.util.jsse.SSLContextParameters</code> in the <a shape="rect" href="registry.html">Registry</a>. <strong>Important:</strong> Only one instance of <code>org.apache.camel.util.jsse.SSLContextParameters</code> is supported per HttpComponent. If you need to use 2 or more different instances, you need to define a new HttpComponent per instance you need. See further below for more details. See <a shape="rect" href="#HTTP4-UsingtheJSSEConfigurationUtility">Using the JSS
E Configuration Utility</a>. Use the <code>sslContextParameters</code> option instead. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>sslContextParameters</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.11.1:</strong> Reference to a <code>org.apache.camel.util.jsse.SSLContextParameters</code> in the <a shape="rect" href="registry.html">Registry</a>. <strong>Important:</strong> Only one instance of <code>org.apache.camel.util.jsse.SSLContextParameters</code> is supported per HttpComponent. If you need to use 2 or more different instances, you need to define a new HttpComponent per instance you need. See further below for more details. See <a shape="rect" href="#HTTP4-UsingtheJSSEConfigurationUtility">Using the JSSE Configuration Utility</a>. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>x509HostnameVerifier<
/code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>BrowserCompatHostnameVerifier</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.7:</strong> You can refer to a different <code>org.apache.http.conn.ssl.X509HostnameVerifier</code> instance in the <a shape="rect" href="registry.html">Registry</a> such as <code>org.apache.http.conn.ssl.StrictHostnameVerifier</code> or <code>org.apache.http.conn.ssl.AllowAllHostnameVerifier</code>. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>urlRewrite</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.11:</strong> <strong>Producer only</strong> Refers to a custom <code>org.apache.camel.component.http4.UrlRewrite</code> which allows you to rewrite urls when you bridge/proxy endpoints. See more details at <a shape="rect" href="urlrewrite.html">UrlRewr
ite</a> and <a shape="rect" href="how-to-use-camel-as-a-http-proxy-between-a-client-and-server.html">How to use Camel as a HTTP proxy between a client and server</a>. </p></td></tr></tbody></table></div>
+<p>The following authentication options can also be set on the HttpEndpoint:</p><h4 id="HTTP4-SettingBasicAuthenticationandProxy">Setting Basic Authentication and Proxy</h4><p><strong>Before Camel 2.8.0</strong></p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Default Value </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>username</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Username for authentication. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>password</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Password
for authentication. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>domain</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The domain name for authentication. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>host</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The host name authentication. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>proxyHost</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The proxy host name </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>proxyPort</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td cols
pan="1" rowspan="1" class="confluenceTd"><p> The proxy port number </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>proxyUsername</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Username for proxy authentication </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>proxyPassword</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Password for proxy authentication </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>proxyDomain</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The proxy domain name </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>proxyNtHost</code> </p></td><td colspan="1" r
owspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The proxy Nt host name </p></td></tr></tbody></table></div>
+<p><strong>Since Camel 2.8.0</strong></p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Default Value </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>authUsername</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Username for authentication </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>authPassword</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Password for authentication </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>authDomain</code> </p></td><td colspan="1" rowspan="1" class="confluenc
eTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The domain name for authentication </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>authHost</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The host name authentication </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>proxyAuthHost</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The proxy host name </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>proxyAuthPort</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The proxy port number </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>proxyAuthS
cheme</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The proxy scheme, will fallback and use the scheme from the endpoint if not configured. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>proxyAuthUsername</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Username for proxy authentication </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>proxyAuthPassword</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Password for proxy authentication </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>proxyAuthDomain</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colsp
an="1" rowspan="1" class="confluenceTd"><p> The proxy domain name </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>proxyAuthNtHost</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The proxy Nt host name </p></td></tr></tbody></table></div>
+<h3 id="HTTP4-MessageHeaders">Message Headers</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>Exchange.HTTP_URI</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>String</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> URI to call. Will override existing URI set directly on the endpoint. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>Exchange.HTTP_PATH</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>String</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Request URI's path, the header will be used to build the request URI with the HTTP_URI. </p></td></tr><tr><td colspan="
1" rowspan="1" class="confluenceTd"><p> <code>Exchange.HTTP_QUERY</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>String</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> URI parameters. Will override existing URI parameters set directly on the endpoint. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>Exchange.HTTP_RESPONSE_CODE</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>int</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The HTTP response code from the external server. Is 200 for OK. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>Exchange.HTTP_CHARACTER_ENCODING</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>String</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Character encoding. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>Exchange.CONTENT_TYPE
</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>String</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The HTTP content type. Is set on both the IN and OUT message to provide a content type, such as <code>text/html</code>. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>Exchange.CONTENT_ENCODING</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>String</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The HTTP content encoding. Is set on both the IN and OUT message to provide a content encoding, such as <code>gzip</code>. </p></td></tr></tbody></table></div>
<h3 id="HTTP4-MessageBody">Message Body</h3><p>Camel will store the HTTP response from the external server on the OUT body. All headers from the IN message will be copied to the OUT message, so headers are preserved during routing. Additionally Camel will add the HTTP response headers as well to the OUT message headers.</p><h3 id="HTTP4-Responsecode">Response code</h3><p>Camel will handle according to the HTTP response code:</p><ul class="alternate"><li>Response code is in the range 100..299, Camel regards it as a success response.</li><li>Response code is in the range 300..399, Camel regards it as a redirection response and will throw a <code>HttpOperationFailedException</code> with the information.</li><li><p>Response code is 400+, Camel regards it as an external server failure and will throw a <code>HttpOperationFailedException</code> with the information.</p> <div class="aui-message success shadowed information-macro">
<p class="title">throwExceptionOnFailure</p>
<span class="aui-icon icon-success">Icon</span>
Modified: websites/production/camel/content/index.html
==============================================================================
--- websites/production/camel/content/index.html (original)
+++ websites/production/camel/content/index.html Tue Feb 18 07:21:04 2014
@@ -36,17 +36,6 @@
<![endif]-->
- <link href='//camel.apache.org/styles/highlighter/styles/shCoreCamel.css' rel='stylesheet' type='text/css' />
- <link href='//camel.apache.org/styles/highlighter/styles/shThemeCamel.css' rel='stylesheet' type='text/css' />
- <script src='//camel.apache.org/styles/highlighter/scripts/shCore.js' type='text/javascript'></script>
- <script src='//camel.apache.org/styles/highlighter/scripts/shBrushJava.js' type='text/javascript'></script>
- <script src='//camel.apache.org/styles/highlighter/scripts/shBrushXml.js' type='text/javascript'></script>
- <script src='//camel.apache.org/styles/highlighter/scripts/shBrushPlain.js' type='text/javascript'></script>
-
- <script type="text/javascript">
- SyntaxHighlighter.defaults['toolbar'] = false;
- SyntaxHighlighter.all();
- </script>
<title>
Apache Camel: Index
@@ -86,8 +75,8 @@
<tbody>
<tr>
<td valign="top" width="100%">
-<div class="wiki-content maincontent"><div class="sectionColumnWrapper"><div class="sectionMacro"><div class="sectionMacroRow"><div class="columnMacro"><strong><a shape="rect" href="download.html" title="Download">Download it Today!</a></strong><br clear="none">
-<span class="image-wrap" style=""><img src="http://camel.apache.org/images/camel-box-small.png" alt="Camel Box" style="border: 0px solid black"></span></div><div class="columnMacro">Apache Camel ™ is a versatile open-source integration framework based on known <a shape="rect" href="enterprise-integration-patterns.html">Enterprise Integration Patterns</a>.
+<div class="wiki-content maincontent"><div class="sectionColumnWrapper"><div class="sectionMacro"><div class="sectionMacroRow"><div class="columnMacro"><p><strong><a shape="rect" href="download.html">Download it Today!</a></strong><br clear="none">
+<img class="confluence-embedded-image confluence-external-resource" alt="Camel Box" src="http://camel.apache.org/images/camel-box-small.png" data-image-src="http://camel.apache.org/images/camel-box-small.png"></p></div><div class="columnMacro">Apache Camel ™ is a versatile open-source integration framework based on known <a shape="rect" href="enterprise-integration-patterns.html">Enterprise Integration Patterns</a>.
<p>Camel empowers you to define routing and mediation rules in a variety of domain-specific languages, including a Java-based <a shape="rect" href="dsl.html">Fluent API</a>, <a shape="rect" href="spring.html">Spring</a> or <a shape="rect" href="using-osgi-blueprint-with-camel.html">Blueprint</a> <a shape="rect" href="xml-configuration.html">XML Configuration</a> files, and a <a shape="rect" href="scala-dsl.html">Scala DSL</a>. This means you get smart completion of routing rules in your IDE, whether in a Java, Scala or XML editor.</p>
Modified: websites/production/camel/content/pdf-documentation-guide.html
==============================================================================
--- websites/production/camel/content/pdf-documentation-guide.html (original)
+++ websites/production/camel/content/pdf-documentation-guide.html Tue Feb 18 07:21:04 2014
@@ -102,7 +102,7 @@
<p>The camel project uses this wiki to generate it's PDF based documentation. It uses the a <a shape="rect" class="external-link" href="http://www.alistapart.com/articles/boom" rel="nofollow">Boom CSS based style sheet</a> in conjunction with <a shape="rect" class="external-link" href="http://www.princexml.com/download/" rel="nofollow">prince</a> to generate the PDF manuals. The <a shape="rect" href="book-in-one-page.html" title="Book In One Page">Book In One Page</a> stitches together wiki content found through this wiki into a single page with is subsequently downloaded by the PDF generator and transformed into a PDF. This section will help you understand how to best use the wiki markup so that it generates good looking PDF pages.</p></div>
-<p></p><div class="chapter page-reset" id="chapter-tables-and-figures">
+<p></p><p></p><div class="chapter page-reset" id="chapter-tables-and-figures"><p></p>
<h1 id="PDFDocumentationGuide-Images">Images</h1>
<p>Images show up differently on the web than on print. You normally need large images with a high DPI for them to print nicely on paper. This chapter will show you how to control the image sizing properties for PDF output.</p>
@@ -132,9 +132,9 @@
<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> 72 DPI </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> 200 DPI </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> 300 DPI </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> 600 DPI </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <img class="confluence-embedded-image confluence-external-resource" src="http://activemq.apache.org/camel/download.data/camel-box-v1.0-150x200.png" data-image-src="http://activemq.apache.org/camel/download.data/camel-box-v1.0-150x200.png"> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <img class="confluence-embedded-image confluence-external-resource" src="http://activemq.apache.org/camel/download.data/camel-box-v1.0-150x200.png" data-image-src="http://activemq.apache.org/camel/download.data/camel-box-v1.0-150x200.png"> </p></td><td colspan="1" rowspan="1" class="conf
luenceTd"><p> <img class="confluence-embedded-image confluence-external-resource" src="http://activemq.apache.org/camel/download.data/camel-box-v1.0-150x200.png" data-image-src="http://activemq.apache.org/camel/download.data/camel-box-v1.0-150x200.png"> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <img class="confluence-embedded-image confluence-external-resource" src="http://activemq.apache.org/camel/download.data/camel-box-v1.0-150x200.png" data-image-src="http://activemq.apache.org/camel/download.data/camel-box-v1.0-150x200.png"> </p></td></tr></tbody></table></div>
-<p></p></div>
+<p></p><p></p></div><p></p>
-<p></p><div class="chapter page-reset" id="chapter-tables-and-figures">
+<p></p><p></p><div class="chapter page-reset" id="chapter-tables-and-figures"><p></p>
<h1 id="PDFDocumentationGuide-TablesFiguresandListings">Tables Figures and Listings</h1>
<p>Using the BOOM micro format to add captions to tables and headings. We should really create some confluence macros for this.</p>
@@ -156,12 +156,12 @@
</div></div>
<p>To produce:<br clear="none">
-</p><div class="table"><p class="caption">
+</p><p></p><div class="table"><p class="caption">
Example Table
-</p>
+</p><p></p>
<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Table </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Heading </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> value1 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> value2 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> value3 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> value 4 </p></td></tr></tbody></table></div>
-<p></p></div>
+<p></p><p></p></div><p></p>
<div class="section" id="figures">
<h2><a shape="rect" name="PDFDocumentationGuide-CaptionedFigures"></a>Captioned Figures</h2></div>
@@ -179,12 +179,12 @@
</div></div>
<p>To produce:<br clear="none">
-</p><div class="figure"><p class="art">
- <img class="confluence-embedded-image confluence-external-resource" src="http://activemq.apache.org/camel/download.data/camel-box-v1.0-150x200.png" data-image-src="http://activemq.apache.org/camel/download.data/camel-box-v1.0-150x200.png">
+</p><p></p><div class="figure"><p class="art">
+</p> <img class="confluence-embedded-image confluence-external-resource" src="http://activemq.apache.org/camel/download.data/camel-box-v1.0-150x200.png" data-image-src="http://activemq.apache.org/camel/download.data/camel-box-v1.0-150x200.png"> <p>
</p><p class="caption">
Example Figure.
</p></div>
-
+<p></p>
<div class="section" id="listings">
<h2><a shape="rect" name="PDFDocumentationGuide-CaptionedListings"></a>Captioned Listings</h2></div>
@@ -217,7 +217,7 @@
]]></script>
</div></div>
-<p></p></div></div>
+<p></p><p></p></div><p></p></div>
</td>
<td valign="top">
<div class="navigation">
Modified: websites/production/camel/content/release-guide.html
==============================================================================
--- websites/production/camel/content/release-guide.html (original)
+++ websites/production/camel/content/release-guide.html Tue Feb 18 07:21:04 2014
@@ -41,6 +41,7 @@
<script src='//camel.apache.org/styles/highlighter/scripts/shCore.js' type='text/javascript'></script>
<script src='//camel.apache.org/styles/highlighter/scripts/shBrushJava.js' type='text/javascript'></script>
<script src='//camel.apache.org/styles/highlighter/scripts/shBrushXml.js' type='text/javascript'></script>
+ <script src='//camel.apache.org/styles/highlighter/scripts/shBrushPlain.js' type='text/javascript'></script>
<script type="text/javascript">
SyntaxHighlighter.defaults['toolbar'] = false;
@@ -86,7 +87,7 @@
<tr>
<td valign="top" width="100%">
<div class="wiki-content maincontent"><h1 id="ReleaseGuide-HowtocreateandannounceaCamelrelease.">How to create and announce a Camel release.</h1><p>This release guide is based on the <a shape="rect" class="external-link" href="http://maven.apache.org/developers/release/apache-release.html">General guide for releasing Maven-based projects at Apache</a>, so be sure to check it out before continuing and meet all prerequisites.</p><p><strong>Note</strong>: Make sure that you are using <strong>JDK 6</strong>. However for releasing Camel 2.12.0 onwards better use <strong>JDK 7</strong>, this for the sake of the new <a shape="rect" class="external-link" href="http://camel.apache.org/endpoint-annotations.html">HTML documentation feature</a> which doesn't work properly because of misbehaving annotation processing in <strong>JDK 6</strong>.</p><h2 id="ReleaseGuide-Prerequisites">Prerequisites</h2><p>To prepare or perform a release you MUST BE at least an Apache Camel committer.</p><ul><li>The
artifacts for each and every release must be SIGNED; your public key should be added to the KEYS file</li><li>Your public key must also be cross-signed by other Apache committers (this can be done at key signing parties at ApacheCon for instance)</li><li>Make sure you have the correct maven configuration in <code>~/.m2/settings.xml</code></li><li>From Camel 2.10 onwards we will require to use Maven [3.0.2,3.1.0)</li><li>From Camel 2.11 onwards we will require to use Maven [3.0.4,3.1.0]</li><li>You may want to get familiar with the release settings in the parent apache POM.</li><li>Make sure you have installed <a shape="rect" class="external-link" href="http://www.princexml.com/" rel="nofollow">Prince</a> to be able to generate the Camel manual</li><li><p>Add your Prince installation <code>bin</code> directory to your <code>PATH</code> variable:</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[PATH=$PATH:/usr/local/bin/prince
+<script class="theme: Default; brush: text; gutter: false" type="syntaxhighlighter"><![CDATA[PATH=$PATH:/usr/local/bin/prince
]]></script>
</div></div></li></ul><h2 id="ReleaseGuide-Maven2Setup">Maven 2 Setup</h2><p>Before you deploy anything to the maven repository using Maven 2, you should configure your ~/.m2/settings.xml file so that the file permissions of the deployed artifacts are group writable. If you do not do this, other developers will not able to overwrite your SNAPSHOT releases with newer versions. The settings follow the <a shape="rect" class="external-link" href="http://maven.apache.org/developers/committer-settings.html">guidelines </a> used by the Maven project. Please pay particular attention to the <a shape="rect" class="external-link" href="http://maven.apache.org/guides/mini/guide-encryption.html">password encryption recommendations</a>.</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[<settings>
@@ -138,57 +139,57 @@
</settings>
]]></script>
</div></div><p>It is also essential that you configure your umask to 2 on people.apache.org for non-interactive login. You can do that by including the snipped below in your <code>.profile</code>.</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[umask 002
+<script class="theme: Default; brush: text; gutter: false" type="syntaxhighlighter"><![CDATA[umask 002
]]></script>
</div></div><h3 id="ReleaseGuide-CreatingtheCamelRelease">Creating the Camel Release</h3><p>The release plugin will prompt for a release version, tag and next release version. Use a three digit release version of the form: 2.x.x and for the tag use a string of the form: camel-2.x.x. The next version string should use the two digit from: 2.x-SNAPSHOT as this can be consistent for future SNAPSHOT releases.</p><ol><li><p>Grab the latest source from Git</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[git clone https://git-wip-us.apache.org/repos/asf/camel.git
+<script class="theme: Default; brush: text; gutter: false" type="syntaxhighlighter"><![CDATA[git clone https://git-wip-us.apache.org/repos/asf/camel.git
cd camel
]]></script>
</div></div></li><li><p>Verify headers with <a shape="rect" class="external-link" href="http://incubator.apache.org/rat/apache-rat-plugin/usage.html">rat</a></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[mvn -e org.apache.rat:apache-rat-plugin:check
+<script class="theme: Default; brush: text; gutter: false" type="syntaxhighlighter"><![CDATA[mvn -e org.apache.rat:apache-rat-plugin:check
grep -e ' !?????' target/rat.txt -- will show any files without licenses
]]></script>
</div></div> <div class="aui-message hint shadowed information-macro">
<span class="aui-icon icon-hint">Icon</span>
<div class="message-content">
<p>Because of <a shape="rect" class="external-link" href="http://jira.codehaus.org/browse/MRELEASE-812" rel="nofollow">MRELEASE-812</a>, you should use the following setting:</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[LANG='en_US.UTF-8'
+<script class="theme: Default; brush: text; gutter: false" type="syntaxhighlighter"><![CDATA[LANG='en_US.UTF-8'
]]></script>
</div></div>
</div>
</div>
</li><li><p>Do a release dry run to check for problems</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[mvn release:prepare -DdryRun=true
+<script class="theme: Default; brush: text; gutter: false" type="syntaxhighlighter"><![CDATA[mvn release:prepare -DdryRun=true
]]></script>
</div></div><p>Check that you are happy with the results. The poms for the proposed tags will be in pom.xml.tag. Check also the generated signature files:</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[cmueller$ gpg camel-core/target/camel-core-2.7.5-SNAPSHOT.jar.asc
+<script class="theme: Default; brush: text; gutter: false" type="syntaxhighlighter"><![CDATA[cmueller$ gpg camel-core/target/camel-core-2.7.5-SNAPSHOT.jar.asc
gpg: Signature made Tue Jan 10 20:50:27 2012 CET using RSA key ID 2A239C2C
gpg: Good signature from "Christian Mueller (CODE SIGNING KEY) <cmueller@apache.org>"
]]></script>
</div></div><p>When you like the results, clean up:</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[mvn release:clean
+<script class="theme: Default; brush: text; gutter: false" type="syntaxhighlighter"><![CDATA[mvn release:clean
]]></script>
</div></div></li><li><p>Prepare the release</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[mvn release:prepare
+<script class="theme: Default; brush: text; gutter: false" type="syntaxhighlighter"><![CDATA[mvn release:prepare
]]></script>
</div></div><p>This will create the tag in svn and leave various stuff around locally to direct the perform phase.</p> <div class="aui-message hint shadowed information-macro">
<span class="aui-icon icon-hint">Icon</span>
<div class="message-content">
<p><strong>Note:</strong> If you're located in Europe then release:prepare may fail with '<em>Unable to tag SCM</em>' and '<em>svn: No such revision X</em>'. Wait 10 seconds and run</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[mvn release:prepare
+<script class="theme: Default; brush: text; gutter: false" type="syntaxhighlighter"><![CDATA[mvn release:prepare
]]></script>
</div></div><p>again.</p>
</div>
</div>
</li><li><p>Perform the release to the staging repo</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[mvn release:perform
+<script class="theme: Default; brush: text; gutter: false" type="syntaxhighlighter"><![CDATA[mvn release:perform
]]></script>
</div></div></li><li>Close the staging repository<br clear="none"> Quote from the <a shape="rect" class="external-link" href="http://maven.apache.org/developers/release/apache-release.html">Maven release guide for Apache projects</a><blockquote><p>Login to <a shape="rect" class="external-link" href="https://repository.apache.org">https://repository.apache.org</a> using your Apache LDAP credentials. Click on "Staging Repositories". Then select "org.apache.camel-xxx" in the list of repositories, where xxx represents your username and ip. Click "Close" on the tool bar above. This will close the repository from future deployments and make it available for others to view. If you are staging multiple releases together, skip this step until you have staged everything. Enter the name and version of the artifact being released in the "Description" field and then click "Close". This will make it easier to identify it later.</p></blockquote>See the image in the original guide for more info.</l
i><li>Verify staged artifacts<br clear="none"> Quote from the <a shape="rect" class="external-link" href="http://maven.apache.org/developers/release/apache-release.html">original guide</a><blockquote><p>If you click on your repository, a tree view will appear below. You can then browse the contents to ensure the artifacts are as you expect them. Pay particular attention to the existence of *.asc (signature) files. If the you don't like the content of the repository, right click your repository and choose "Drop". You can then rollback your release and repeat the process.<br clear="none"> Note the repository URL, you will need this in your vote email.</p></blockquote></li></ol><h2 id="ReleaseGuide-TestingtheCamelReleaseCandidate">Testing the Camel Release Candidate</h2><p>When folks need to test out a release candidate, the jars will not have been uploaded to the central Maven repo. This means that the example programs which use Maven will not automatically work and you need to follow
the <a shape="rect" href="testing-a-release-candidate.html">Testing a release candidate</a> guidelines.<br clear="none"> Afterwards send out the VOTE for this release candidate to the dev@ mailing list.</p><h2 id="ReleaseGuide-Manuallyupdatingfiles">Manually updating files</h2><p>The <code>pom.xml</code> files in <code>etc</code>, <code>tests/camel-itest-karaf</code>, <code>tests/camel-itest-osgi</code>, <code>tests/camel-itest-performance</code> and <code>tests/camel-performance</code> need to be manually updated with the Camel version number in the <code><parent></code> tag.</p><h2 id="ReleaseGuide-AnnouncingtheCamelRelease">Announcing the Camel Release</h2><p>If the VOTE pass,</p><ol><li>Close it by sending the RESULT to the mailing list.</li><li>Promote the artifacts to the central repo. For this login to <a shape="rect" class="external-link" href="https://repository.apache.org">https://repository.apache.org</a> using your Apache LDAP credentials. Click on "Staging Reposi
tories". Select "org.apache.camel-xxx" in the list of repositories, where xxx represents your username and ip. Click "Release" on the tool bar above. This will promote all artifacts to the central maven repo. Enter the name and version of the artifact being released in the "Description" field and then click "Release". This will make it easier to identify it later.</li><li>Perform a <a shape="rect" class="external-link" href="https://issues.apache.org/jira/plugins/servlet/project-config/CAMEL/versions">release in JIRA</a> and create a new release version in JIRA</li><li>There should be already a release notes page in the <a shape="rect" href="in-progress.html">In Progress</a> folder (if not create one based on the <a shape="rect" href="camel-xyz-release-template.html">Camel x.y.z Release (template)</a>). Edit it and change the number of fixed issues and update its parent to be the <a shape="rect" href="download.html">Download</a> page. Now would be a good time to create a new release
notes page for the next release based on the template mentioned before. It is useful and simpler to keep it up to date during the development cycle.</li><li><p>Copy the newly deployed distribution to Apache website:</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[cd ${CAMEL_ROOT_DIR}/etc/scripts
+<script class="theme: Default; brush: text; gutter: false" type="syntaxhighlighter"><![CDATA[cd ${CAMEL_ROOT_DIR}/etc/scripts
release-distro.sh <Camel version>
]]></script>
</div></div><p>Check the console output and finish this step manually after checking the artifacts.</p></li><li>Copy the KEYS file by ssh into /www/www.apache.org/dist/camel/apache-camel/ on people.apache.org <strong>if</strong> you changed it</li><li>Update the <a shape="rect" href="download.html">Download</a> page to refer to the latest release distributions (search & replace the version numbers mostly)</li><li><p>Upload the newly deployed schema and the manual to Apache:</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[cd ${CAMEL_ROOT_DIR}/etc/scripts
+<script class="theme: Default; brush: text; gutter: false" type="syntaxhighlighter"><![CDATA[cd ${CAMEL_ROOT_DIR}/etc/scripts
release-website.sh <Camel version>
]]></script>
</div></div><p>Check the console output and finish this step manually after checking the artifacts.</p></li><li><p>Upload the javadocs to Apache, you need to checkout the files from "https://svn.apache.org/repos/infra/websites/production/camel/content/maven/"</p> <div class="aui-message hint shadowed information-macro">
@@ -210,18 +211,18 @@ Certificate information:
</div>
</div>
<ol><li>Copy $<code>CAMEL_ROOT</code>/trunk/etc/scripts/release-website.sh to your home directory on people.apache.org</li><li>Execute this script, e.g: ./release-website.sh 2.10.0<ol><li>It will download the XML Schema files and the Camel manual for the given release version</li><li>At the end you have to commit these changes manually to SVN (simply follow the instructions)</li></ol></li></ol></li><li>Update the <a shape="rect" href="xml-reference.html">Xml Reference</a> page with a link to the XSD's</li><li>Update the <a shape="rect" href="manual.html">Manual</a> page with a link to the PDF/HTML <strong>if</strong> it's a new major/minor version</li><li>Mail the <a shape="rect" class="external-link" href="mailto:dev@camel.apache.org" rel="nofollow">dev</a>, <a shape="rect" class="external-link" href="mailto:user@camel.apache.org" rel="nofollow">user</a> & <a shape="rect" class="external-link" href="mailto:announce@apache.org" rel="nofollow">announce</a> lists</li><li><a shape=
"rect" href="https://cwiki.apache.org/confluence/pages/createblogpost.action?spaceKey=CAMEL">Post</a> a news entry in the wiki which <strong>links to the release page</strong> so folks can download it!</li><li>perform a full export of the Camel WIKI sites to see your blog on the Camel index site. To do this, you have to remove the main.pageCache file in the content/cache sub directory:<ol><li>execute: svn rm <a shape="rect" class="external-link" href="https://svn.apache.org/repos/infra/websites/production/camel/content/cache/main.pageCache">https://svn.apache.org/repos/infra/websites/production/camel/content/cache/main.pageCache</a></li></ol></li><li>Add the release version number to the following <code>spring.schemas</code> file located in <code>src/main/resources/META-INF</code> directory of the following components:<br clear="none"> camel-cxf<br clear="none"> camel-spring<br clear="none"> camel-spring-integration<br clear="none"> camel-spring-security</li><li>Have a beer! <img cl
ass="emoticon emoticon-smile" src="https://cwiki.apache.org/confluence/s/en_GB-1988229788/4109/76e0dbb30bc8580e459c201f3535d84f9283a9ac.1/_/images/icons/emoticons/smile.png" data-emoticon-name="smile" alt="(smile)"></li></ol><h2 id="ReleaseGuide-Createanewmaintenancebranch">Create a new maintenance branch</h2><p>When we finish the major version release, we need to create a maintenance branch to holds the bug fixes. Here are the steps for it.</p><ol><li><p>Create a branch from trunk remotely</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[svn copy -m "create camel 2.10.x fix branch" https://svn.apache.org/repos/asf/camel/trunk/ https://svn.apache.org/repos/asf/camel/branches/camel-2.10.x
+<script class="theme: Default; brush: text; gutter: false" type="syntaxhighlighter"><![CDATA[svn copy -m "create camel 2.10.x fix branch" https://svn.apache.org/repos/asf/camel/trunk/ https://svn.apache.org/repos/asf/camel/branches/camel-2.10.x
]]></script>
</div></div></li></ol><ol><li><p>Check out the remote branch in a new directory</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[svn checkout https://svn.apache.org/repos/asf/camel/branches/camel-2.10.x
+<script class="theme: Default; brush: text; gutter: false" type="syntaxhighlighter"><![CDATA[svn checkout https://svn.apache.org/repos/asf/camel/branches/camel-2.10.x
]]></script>
</div></div></li></ol><ol><li><p>Initialize merge tracking for the new branch</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[cd camel-2.10.x
+<script class="theme: Default; brush: text; gutter: false" type="syntaxhighlighter"><![CDATA[cd camel-2.10.x
svnmerge.py init -f commit.txt https://svn.apache.org/repos/asf/camel/branches/camel-2.10.x
svn ci -F commit.txt
]]></script>
</div></div></li></ol><ol><li><p>Update the version number for the next patch release</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[find ./ -name pom.xml |xargs perl -pi -e 's/2.11-SNAPSHOT/2.10.x-SNAPSHOT/g'
+<script class="theme: Default; brush: text; gutter: false" type="syntaxhighlighter"><![CDATA[find ./ -name pom.xml |xargs perl -pi -e 's/2.11-SNAPSHOT/2.10.x-SNAPSHOT/g'
svn ci -m "Update the pom version for next patch release"
]]></script>
</div></div></li></ol><ol><li>Set up a new continuous integration build, if we release a new major/minor version: <a shape="rect" class="external-link" href="https://builds.apache.org/view/A-D/view/Camel/">https://builds.apache.org/view/A-D/view/Camel/</a></li></ol></div>