svn commit: r814293 - in /websites/production/camel/content: cache/main.pageCache http4.html

[buildbot]

Author: buildbot
Date: Tue Apr 24 22:18:09 2012
New Revision: 814293

Log:
Production update by buildbot for camel

Modified:
    websites/production/camel/content/cache/main.pageCache
    websites/production/camel/content/http4.html

Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.

Modified: websites/production/camel/content/http4.html
==============================================================================
--- websites/production/camel/content/http4.html (original)
+++ websites/production/camel/content/http4.html Tue Apr 24 22:18:09 2012
@@ -106,7 +106,7 @@ http4:hostname[:port][/resourceUri][?opt
 
 <p>You can append query options to the URI in the following format, 
<tt>?option=value&amp;option=value&amp;...</tt></p>
 
-<div class="panelMacro"><table class="infoMacro"><colgroup span="1"><col 
span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1" 
valign="top"><img align="middle" 
src="https://cwiki.apache.org/confluence/images/icons/emoticons/information.gif";
 width="16" height="16" alt="" border="0"></td><td colspan="1" 
rowspan="1"><b>camel-http4 vs camel-jetty</b><br clear="none">You can produce 
only 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" title="Jetty">Jetty Component</a> 
instead.</td></tr></table></div>
+<div class="panelMacro"><table class="infoMacro"><colgroup span="1"><col 
span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1" 
valign="top"><img align="middle" 
src="https://cwiki.apache.org/confluence/images/icons/emoticons/information.gif";
 width="16" height="16" alt="" border="0"></td><td colspan="1" 
rowspan="1"><b>camel-http4 vs camel-jetty</b><br clear="none">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" title="Jetty">Jetty Component</a> 
instead.</td></tr></table></div>
 
 <h3><a shape="rect" name="HTTP4-HttpEndpointOptions"></a>HttpEndpoint 
Options</h3>