Author: buildbot
Date: Mon Dec 31 16:13:22 2012
New Revision: 844424
Log:
Staging update by buildbot for ode
Modified:
websites/staging/ode/trunk/content/ (props changed)
websites/staging/ode/trunk/content/writing-bpel-test-cases.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 31 16:13:22 2012
@@ -1 +1 @@
-1427159
+1427162
Modified: websites/staging/ode/trunk/content/writing-bpel-test-cases.html
==============================================================================
--- websites/staging/ode/trunk/content/writing-bpel-test-cases.html (original)
+++ websites/staging/ode/trunk/content/writing-bpel-test-cases.html Mon Dec 31
16:13:22 2012
@@ -109,9 +109,9 @@
<p>The 3 first lines specify the namespace, the name and the operation to
which messages will be sent. Then comes the request message. It should always
be named request?, and should always be wrapped in a message element and
another element named like the message part. Finally, and most importantly,
comes the response test pattern. It's a regular expression that will be checked
against the response produced by the process. If the expression can't be found,
the test fails. In the HelloWorld example here we're just testing that our
response includes 'Hello World'.</p>
<p>A test descriptor can contain more that one request/response couple,
allowing several executions of a same process, testing different input/output
combinations. You just need to increase the numbers in the request and response
property names. For an example see the <a
href="http://svn.apache.org/repos/asf/ode/trunk/bpel-test/src/test/resources/bpel/2.0/TestFlowActivity1/test.properties";>descriptor
of the flow test</a>.</p>
<p>Also if your process needs to receive several messages, you can have
several test descriptors, each corresponding to a message. The files should
just be named test1.properties, test2.properties, ... following the order of
invocation. Here is an example with 2 descriptors used by the correlation test
case:</p>
-<div class="codehilite"><pre><span class="err">test1.properties</span>
+<div class="caption">test1.properties</div>
-<span class="na">namespace</span><span class="o">=</span><span
class="s">http://ode/bpel/unit-test/testCorrelation.wsdl</span>
+<div class="codehilite"><pre><span class="na">namespace</span><span
class="o">=</span><span
class="s">http://ode/bpel/unit-test/testCorrelation.wsdl</span>
<span class="na">service</span><span class="o">=</span><span
class="s">testCorrelationService</span>
<span class="na">operation</span><span class="o">=</span><span
class="s">request</span>
<span class="na">request1</span><span class="o">=</span><span
class="s"><message><requestMessageData><testMessage><requestID>Start
Test5.1</requestID><requestText>Event Start</span>
@@ -120,11 +120,9 @@
</pre></div>
-<!-- -->
+<div class="caption">test2.properties</div>
-<div class="codehilite"><pre><span class="err">test2.properties</span>
-
-<span class="na">namespace</span><span class="o">=</span><span
class="s">http://ode/bpel/unit-test/testCorrelation.wsdl</span>
+<div class="codehilite"><pre><span class="na">namespace</span><span
class="o">=</span><span
class="s">http://ode/bpel/unit-test/testCorrelation.wsdl</span>
<span class="na">service</span><span class="o">=</span><span
class="s">testCorrelationService</span>
<span class="na">operation</span><span class="o">=</span><span
class="s">continue</span>
<span class="na">request1</span><span class="o">=</span><span
class="s"><message><requestMessageData><testMessage><requestID>Start
Test5.1</requestID><requestText>Event Start</span>
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 31
16:13:22 2012
@@ -99,6 +99,8 @@
<li><a href="#do-i-need-to-install-rampart-myself">Do I need to install
Rampart myself?</a></li>
<li><a href="#useful-resources">Useful resources</a><ul>
<li><a href="#rampart-material">Rampart material</a></li>
+</ul>
+</li>
<li><a href="#ode-test-cases">ODE test cases</a><ul>
<li><a href="#how-to-run-them">How to run them</a></li>
<li><a href="#where-are-the-processes-executed-by-the-unit-tests">Where are
the processes executed by the unit tests?</a></li>
@@ -108,8 +110,6 @@
</ul>
</li>
</ul>
-</li>
-</ul>
</div>
<div class="alert alert-warning"><h4 class="alert-heading">Only in
1.3.2+</h4></div>
@@ -241,14 +241,14 @@
<li><a href="http://ws.apache.org/rampart/samples.html";>Rampart
samples</a></li>
<li><a
href="https://wiki.internet2.edu/confluence/display/GrouperWG/The+Newcastle+University+Grouper+page";>a
Rampart tutorial</a></li>
</ul>
-<h4 id="ode-test-cases">ODE test cases</h4>
-<h5 id="how-to-run-them">How to run them</h5>
+<h3 id="ode-test-cases">ODE test cases</h3>
+<h4 id="how-to-run-them">How to run them</h4>
<div class="codehilite"><pre>$ cd axis2-war
$ buildr test:Secure
</pre></div>
-<h5 id="where-are-the-processes-executed-by-the-unit-tests">Where are the
processes executed by the unit tests?</h5>
+<h4 id="where-are-the-processes-executed-by-the-unit-tests">Where are the
processes executed by the unit tests?</h4>
<p>The executed processes are generated by the build, so run the tests once,
then look into the following directories. Process directories are prefixed with
"process-".</p>
<ul>
<li>axis2-war/target/test-classes/TestRampartPolicy/secured-services/</li>
@@ -256,7 +256,7 @@ $ buildr test:Secure
<li>axis2-war/target/test-classes/TestRampartBasic/secured-services/</li>
<li>axis2-war/target/test-classes/TestRampartBasic/secured-processes/</li>
</ul>
-<h5 id="the-nitty-gritty-details">the nitty-gritty details</h5>
+<h4 id="the-nitty-gritty-details">the nitty-gritty details</h4>
<p>The integration with Rampart described in this section is tested with a
decent suite of unit tests. These unit tests are based on the <a
href="http://ws.apache.org/rampart/samples.html";>Rampart samples</a>. The <a
href="http://svn.apache.org/repos/asf/webservices/rampart/branches/java/1_3/modules/rampart-samples/";>related
resources</a> were imported into ODE repository.</p>
<p>These tests are divided into two parts: tests using the parameter base
configuration model aka "basic tests" and tests using the policy base
configuration model aka "policy tests".</p>
<p>ODE test cases reuse these test cases in two different scenarii:</p>
