Author: buildbot
Date: Mon Dec 10 18:28:19 2012
New Revision: 841475
Log:
Staging update by buildbot for ode
Modified:
websites/staging/ode/trunk/content/ (props changed)
websites/staging/ode/trunk/content/use-assign-to-build-messages.html
websites/staging/ode/trunk/content/ws-security-in-ode.html
Propchange: websites/staging/ode/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Dec 10 18:28:19 2012
@@ -1 +1 @@
-1419608
+1419633
Modified: websites/staging/ode/trunk/content/use-assign-to-build-messages.html
==============================================================================
--- websites/staging/ode/trunk/content/use-assign-to-build-messages.html
(original)
+++ websites/staging/ode/trunk/content/use-assign-to-build-messages.html Mon
Dec 10 18:28:19 2012
@@ -81,7 +81,27 @@
<div class="row">
<div class="span12">
-
+ <p><a
name="UseAssigntobuildmessages-UseAssigntobuildwholemessageatonce(allparts)"></a></p>
+<h2 id="use-assign-to-build-whole-message-at-once-all-parts">Use Assign to
build whole message at once (all parts)</h2>
+<p>Let's say you have WSDL parts defined as follow:</p>
+<div class="codehilite"><pre><span class="nt"><wsdl:message</span> <span
class="na">name=</span><span class="s">"HelloMessage"</span><span
class="nt">></span>
+ <span class="nt"><wsdl:part</span> <span class="na">name=</span><span
class="s">"part1"</span> <span class="na">type=</span><span
class="s">"xsd:string"</span><span class="nt">/></span>
+ <span class="nt"><wsdl:part</span> <span class="na">name=</span><span
class="s">"part2"</span> <span class="na">type=</span><span
class="s">"xsd:string"</span><span class="nt">/></span>
+<span class="nt"></wsdl:message></span>
+</pre></div>
+
+
+<p>In order to build whole message at once, you need to use following
statement:</p>
+<div class="codehilite"><pre><span class="nt"><assign></span>
+ <span class="nt"><copy></span>
+ <span class="nt"><from><literal><message</span> <span
class="na">xmlns=</span><span class="s">""</span><span
class="nt">><part1></span>abc1<span
class="nt"></part1><part2></span>abc2<span
class="nt"></part2></message></literal></from></span>
+ <span class="nt"><to></span>$myVar<span
class="nt"></to></span>
+ <span class="nt"></copy></span>
+<span class="nt"></assign></span>
+</pre></div>
+
+
+<p>Complete BPEL example is provided here: <a
href="https://svn.apache.org/repos/asf/ode/trunk/axis2-war/src/test/resources/TestMultiPartMessage";>TestMultiPartMessage</a></p>
</div>
</div>
Modified: websites/staging/ode/trunk/content/ws-security-in-ode.html
==============================================================================
--- websites/staging/ode/trunk/content/ws-security-in-ode.html (original)
+++ websites/staging/ode/trunk/content/ws-security-in-ode.html Mon Dec 10
18:28:19 2012
@@ -83,7 +83,7 @@
<div class="span12">
<p><a name="WS-SecurityinODE-HowtouseWS-SecurityinODE?"></a></p>
<h2 id="how-to-use-ws-security-in-ode">How to use WS-Security in ODE?</h2>
-<div class="alert alert-warning"><h4 class="alert-heading"><i
class="icon-warning-sign"></i> Only in 1.3.2</h4></div>
+<div class="alert alert-warning"><h4 class="alert-heading">Only in
1.3.2</h4></div>
<p>ODE 1.3.2 introduces support for WS-Security: secure services can now be
invoked from a process, and the process service itself might be secured. A
first part will explain how to invoke a secured service, a second part how to
secure the process service.</p>
<p>ODE has an <a
href="architectural-overview.html#ODE-Integration-Layers">Integration Layer
based on Axis2</a> so using Rampart, the Axis2 security modules, goes without
saying. As a result this section will only focus on Rampart integration.
Rampart and WS-Security specifications won't be detailed here. Please refer to
their ad-hoc documentations for further details.</p>
