svn commit: r908716 - in /websites/production/camel/content: cache/main.pageCache event-message.html

Tue, 13 May 2014 21:25:30 -0700 

Author: buildbot
Date: Tue May 13 17:17:57 2014
New Revision: 908716

Log:
Production update by buildbot for camel

Modified:
    websites/production/camel/content/cache/main.pageCache
    websites/production/camel/content/event-message.html

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

Modified: websites/production/camel/content/event-message.html
==============================================================================
--- websites/production/camel/content/event-message.html (original)
+++ websites/production/camel/content/event-message.html Tue May 13 17:17:57 
2014
@@ -84,76 +84,38 @@
        <tbody>
         <tr>
         <td valign="top" width="100%">
-<div class="wiki-content maincontent"><h2 id="EventMessage-EventMessage">Event 
Message</h2>
-
-<p>Camel supports the <a shape="rect" class="external-link" 
href="http://www.enterpriseintegrationpatterns.com/EventMessage.html"; 
rel="nofollow">Event Message</a> from the <a shape="rect" 
href="enterprise-integration-patterns.html">EIP patterns</a> by supporting the 
<a shape="rect" href="exchange-pattern.html">Exchange Pattern</a> on a <a 
shape="rect" href="message.html">Message</a> which can be set to 
<strong>InOnly</strong> to indicate a oneway event message. Camel <a 
shape="rect" href="components.html">Components</a> then implement this pattern 
using the underlying transport or protocols.</p>
-
-<p><img class="confluence-embedded-image confluence-external-resource" 
src="http://www.enterpriseintegrationpatterns.com/img/EventMessageSolution.gif"; 
data-image-src="http://www.enterpriseintegrationpatterns.com/img/EventMessageSolution.gif";></p>
-
-<p>The default behaviour of many <a shape="rect" 
href="components.html">Components</a> is InOnly such as for <a shape="rect" 
href="jms.html">JMS</a>, <a shape="rect" href="file2.html">File</a> or <a 
shape="rect" href="seda.html">SEDA</a></p>
-
-    <div class="aui-message success shadowed information-macro">
+<div class="wiki-content maincontent"><h2 id="EventMessage-EventMessage">Event 
Message</h2><p>Camel supports the <a shape="rect" class="external-link" 
href="http://www.enterpriseintegrationpatterns.com/EventMessage.html"; 
rel="nofollow">Event Message</a> from the <a shape="rect" 
href="enterprise-integration-patterns.html">EIP patterns</a> by supporting the 
<a shape="rect" href="exchange-pattern.html">Exchange Pattern</a> on a <a 
shape="rect" href="message.html">Message</a> which can be set to 
<strong>InOnly</strong> to indicate a oneway event message. Camel <a 
shape="rect" href="components.html">Components</a> then implement this pattern 
using the underlying transport or protocols.</p><p><img 
class="confluence-embedded-image confluence-external-resource" 
src="http://www.enterpriseintegrationpatterns.com/img/EventMessageSolution.gif"; 
data-image-src="http://www.enterpriseintegrationpatterns.com/img/EventMessageSolution.gif";></p><p>The
 default behaviour of many <a shape="rect" href="com
 ponents.html">Components</a> is InOnly such as for <a shape="rect" 
href="jms.html">JMS</a>, <a shape="rect" href="file2.html">File</a> or <a 
shape="rect" href="seda.html">SEDA</a></p>    <div class="aui-message success 
shadowed information-macro">
                     <p class="title">Related</p>
                             <span class="aui-icon icon-success">Icon</span>
                 <div class="message-content">
-                            
-<p>See the related <a shape="rect" href="request-reply.html">Request Reply</a> 
message.</p>
+                            <p>See the related <a shape="rect" 
href="request-reply.html">Request Reply</a> message.</p>
                     </div>
     </div>
-
-
-<h3 id="EventMessage-ExplicitlyspecifyingInOnly">Explicitly specifying 
InOnly</h3>
-
-<p>If you are using a component which defaults to InOut you can override the 
<a shape="rect" href="exchange-pattern.html">Exchange Pattern</a> for an 
endpoint using the pattern property.</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[
-foo:bar?exchangePattern=InOnly
+<h3 id="EventMessage-ExplicitlyspecifyingInOnly">Explicitly specifying 
InOnly</h3><p>If you are using a component which defaults to InOut you can 
override the <a shape="rect" href="exchange-pattern.html">Exchange Pattern</a> 
for an endpoint using the pattern property.</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[foo:bar?exchangePattern=InOnly
 ]]></script>
-</div></div>
-
-<p>From 2.0 onwards on Camel you can specify the <a shape="rect" 
href="exchange-pattern.html">Exchange Pattern</a> using the dsl.</p>
-
-<p><strong>Using the <a shape="rect" href="fluent-builders.html">Fluent 
Builders</a></strong></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[
-from(&quot;mq:someQueue&quot;).
-  inOnly().
+</div></div><p>From 2.0 onwards on Camel you can specify the <a shape="rect" 
href="exchange-pattern.html">Exchange Pattern</a> using the 
DSL.</p><p><strong>Using the <a shape="rect" href="fluent-builders.html">Fluent 
Builders</a></strong></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[from(&quot;mq:someQueue&quot;).
+  setExchangePattern(ExchangePattern.InOnly).
   bean(Foo.class);
 ]]></script>
-</div></div>
-
-<p>or you can invoke an endpoint with an explicit pattern</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[
-from(&quot;mq:someQueue&quot;).
+</div></div><p>or you can invoke an endpoint with an explicit pattern</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[from(&quot;mq:someQueue&quot;).
   inOnly(&quot;mq:anotherQueue&quot;);
 ]]></script>
-</div></div>
-
-<p><strong>Using the <a shape="rect" href="spring-xml-extensions.html">Spring 
XML Extensions</a></strong></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[
-&lt;route&gt;
+</div></div><p><strong>Using the <a shape="rect" 
href="spring-xml-extensions.html">Spring XML Extensions</a></strong></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[&lt;route&gt;
     &lt;from uri=&quot;mq:someQueue&quot;/&gt;
     &lt;inOnly uri=&quot;bean:foo&quot;/&gt;
 &lt;/route&gt;
 ]]></script>
-</div></div>
-
-<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[
-&lt;route&gt;
+</div></div><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[&lt;route&gt;
     &lt;from uri=&quot;mq:someQueue&quot;/&gt;
     &lt;inOnly uri=&quot;mq:anotherQueue&quot;/&gt;
 &lt;/route&gt;
 ]]></script>
-</div></div>
-
-<h4 id="EventMessage-UsingThisPattern">Using This Pattern</h4>
+</div></div><p></p><h4 id="EventMessage-UsingThisPattern">Using This 
Pattern</h4>
 
 <p>If you would like to use this EIP Pattern then please read the <a 
shape="rect" href="getting-started.html">Getting Started</a>, you may also find 
the <a shape="rect" href="architecture.html">Architecture</a> useful 
particularly the description of <a shape="rect" 
href="endpoint.html">Endpoint</a> and <a shape="rect" 
href="uris.html">URIs</a>. Then you could try out some of the <a shape="rect" 
href="examples.html">Examples</a> first before trying this pattern 
out.</p></div>
         </td>

Reply via email to