camel-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r908328 - in /websites/production/camel/content: cache/main.pageCache jetty.html
Date Wed, 07 May 2014 18:17:58 GMT
Author: buildbot
Date: Wed May  7 18:17:58 2014
New Revision: 908328

Log:
Production update by buildbot for camel

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

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 Wed May  7 18:17:58 2014
@@ -156,7 +156,7 @@ from("jetty:" + serverUri)
     .otherwise()
     .to("mock:other");
 ]]></script>
-</div></div><p>So if a client sends the HTTP request, <code><a
shape="rect" class="external-link" href="http://serverUri?one=hello" rel="nofollow">http://serverUri?one=hello</a></code>,
the Jetty component will copy the HTTP request parameter, <code>one</code> to
the exchange's <code>in.header</code>. We can then use the <code>simple</code>
language to route exchanges that contain this header to a specific endpoint and all others
to another. If we used a language more powerful than <a shape="rect" href="simple.html">Simple</a>--<span
style="text-decoration: line-through;">such as</span> <span style="text-decoration:
line-through;"><a shape="rect" href="el.html">EL</a></span> <span
style="text-decoration: line-through;">or</span> <span style="text-decoration:
line-through;"><a shape="rect" href="ognl.html">OGNL</a></span>--we could
also test for the parameter value and do routing based on the header value as well.</p><h3
id="Jetty-SessionSupport">Session Support</h3><p>The session su
 pport option, <code>sessionSupport</code>, can be used to enable a <code>HttpSession</code>
object and access the session object while processing the exchange. For example, the following
route enables sessions:</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
+</div></div><p>So if a client sends the HTTP request, <code><a
shape="rect" class="external-link" href="http://serverUri?one=hello" rel="nofollow">http://serverUri?one=hello</a></code>,
the Jetty component will copy the HTTP request parameter, <code>one</code> to
the exchange's <code>in.header</code>. We can then use the <code>simple</code>
language to route exchanges that contain this header to a specific endpoint and all others
to another. If we used a language more powerful than <a shape="rect" href="simple.html">Simple</a>&#160;(such
as <a shape="rect" href="el.html">EL</a> or <a shape="rect" href="ognl.html">OGNL</a>)&#160;we
could also test for the parameter value and do routing based on the header value as well.</p><h3
id="Jetty-SessionSupport">Session Support</h3><p>The session support option,
<code>sessionSupport</code>, can be used to enable a <code>HttpSession</code>
object and access the session object while processing the exchange. For example, the following
route enabl
 es sessions:</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[&lt;route&gt;
     &lt;from uri=&quot;jetty:http://0.0.0.0/myapp/myservice/?sessionSupport=true&quot;/&gt;
     &lt;processRef ref=&quot;myCode&quot;/&gt;



Mime
View raw message