You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@ode.apache.org by bu...@apache.org on 2012/12/31 17:11:00 UTC
svn commit: r844423 - in /websites/staging/ode/trunk/content: ./
http-authentication.html use-assign-to-build-messages.html
writing-bpel-test-cases.html ws-security-in-ode.html
Author: buildbot
Date: Mon Dec 31 16:11:00 2012
New Revision: 844423
Log:
Staging update by buildbot for ode
Modified:
websites/staging/ode/trunk/content/ (props changed)
websites/staging/ode/trunk/content/http-authentication.html
websites/staging/ode/trunk/content/use-assign-to-build-messages.html
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:11:00 2012
@@ -1 +1 @@
-1427157
+1427159
Modified: websites/staging/ode/trunk/content/http-authentication.html
==============================================================================
--- websites/staging/ode/trunk/content/http-authentication.html (original)
+++ websites/staging/ode/trunk/content/http-authentication.html Mon Dec 31 16:11:00 2012
@@ -160,9 +160,10 @@
<span class="nt"></xs:element></span>
<span class="nt"></xs:schema></span>
+</pre></div>
-You can add this schema to your project to allow tools to display/validate the correct element structure.
-</pre></div>
+
+<p>You can add this schema to your project to allow tools to display/validate the correct element structure.</p>
</div>
</div>
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 31 16:11:00 2012
@@ -28,7 +28,7 @@
<li class="">
<a href="/getting-ode.html">Getting ODE</a>
</li>
- <li class=" dropdown">
+ <li class="active dropdown">
<a href="/user-guide.html" class="dropdown-toggle" data-toggle="dropdown" data-target="#">Documentation<b class="caret"></b></a>
<ul class="dropdown-menu">
<li><a href="/userguide/">User Guide</a></li>
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:11:00 2012
@@ -28,7 +28,7 @@
<li class="">
<a href="/getting-ode.html">Getting ODE</a>
</li>
- <li class=" dropdown">
+ <li class="active dropdown">
<a href="/user-guide.html" class="dropdown-toggle" data-toggle="dropdown" data-target="#">Documentation<b class="caret"></b></a>
<ul class="dropdown-menu">
<li><a href="/userguide/">User Guide</a></li>
@@ -98,44 +98,44 @@
<h3 id="test-descriptor">Test Descriptor</h3>
<p>So to begin with your test process must at least have a <a href="http://svn.apache.org/repos/asf/ode/trunk/bpel-test/src/test/resources/bpel/2.0/HelloWorld2/HelloWorld2.bpel">BPEL file</a>, a <a href="http://svn.apache.org/repos/asf/ode/trunk/bpel-test/src/test/resources/bpel/2.0/HelloWorld2/HelloWorld2.wsdl">WSDL file</a> and the standard <a href="http://svn.apache.org/repos/asf/ode/trunk/bpel-test/src/test/resources/bpel/2.0/HelloWorld2/deploy.xml">deploy.xml</a> deployment descriptor (links are provided for the HelloWorld test case). All of these should be included in a single directory.</p>
<p>Then for the test framework to know what it should do you will also need to write a simple test descriptor. It's a simple properties file saying which service is implemented by the process and which messages should be sent to start it and make it continue. It should me named test?.properties with the '?' being a increasing number. Here is the descriptor for the HelloWorld example, in test1.properties:</p>
-<div class="codehilite"><pre>namespace=http://ode/bpel/unit-test.wsdl
-service=HelloService
-operation=hello
-request1=<message><TestPart>Hello</TestPart></message>
-response1=.*Hello World.*
+<div class="codehilite"><pre><span class="na">namespace</span><span class="o">=</span><span class="s">http://ode/bpel/unit-test.wsdl</span>
+<span class="na">service</span><span class="o">=</span><span class="s">HelloService</span>
+<span class="na">operation</span><span class="o">=</span><span class="s">hello</span>
+<span class="na">request1</span><span class="o">=</span><span class="s"><message><TestPart>Hello</TestPart></message></span>
+<span class="na">response1</span><span class="o">=</span><span class="s">.*Hello World.*</span>
</pre></div>
<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>test1.properties
+<div class="codehilite"><pre><span class="err">test1.properties</span>
-namespace=http://ode/bpel/unit-test/testCorrelation.wsdl
-service=testCorrelationService
-operation=request
-request1=<message><requestMessageData><testMessage><requestID>Start Test5.1</requestID><requestText>Event Start
-Test5.1</requestText><requestEnd>no</requestEnd></testMessage></requestMessageData></message>
-response1=ASYNC
+<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>
+<span class="err">Test5.1</requestText><requestEnd>no</requestEnd></testMessage></requestMessageData></message></span>
+<span class="na">response1</span><span class="o">=</span><span class="s">ASYNC</span>
</pre></div>
<!-- -->
-<div class="codehilite"><pre>test2.properties
+<div class="codehilite"><pre><span class="err">test2.properties</span>
-namespace=http://ode/bpel/unit-test/testCorrelation.wsdl
-service=testCorrelationService
-operation=continue
-request1=<message><requestMessageData><testMessage><requestID>Start Test5.1</requestID><requestText>Event Start
-Test5.2.1</requestText><requestEnd>yes</requestEnd></testMessage></requestMessageData></message>
-response1=.*Event Start Test5.1 -&gt; loop on receive until message includes requestEnd = yes -&gt; received
- message -&gt; process complete.*
+<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>
+<span class="err">Test5.2.1</requestText><requestEnd>yes</requestEnd></testMessage></requestMessageData></message></span>
+<span class="na">response1</span><span class="o">=</span><span class="s">.*Event Start Test5.1 -&gt; loop on receive until message includes requestEnd = yes -&gt; received</span>
+ <span class="err">message</span> <span class="err">-&gt</span><span class="c">; process complete.*</span>
</pre></div>
<p>Finally a response can be marked as being ASYNC in the case no reply is expected for a given receive. This only applies to non instantiating receives:</p>
-<div class="codehilite"><pre>response1=ASYNC
+<div class="codehilite"><pre><span class="na">response1</span><span class="o">=</span><span class="s">ASYNC</span>
</pre></div>
@@ -207,8 +207,8 @@ response1=.*Event Start Test5.1 -&gt
<p>The returned data is finally tested by using a nice regular expression for the response:</p>
-<div class="codehilite"><pre>response1=.*Event Start Test5.1 -&gt; loop on receive until message includes requestEnd = yes -&gt;
- received message -&gt; process complete.*
+<div class="codehilite"><pre><span class="na">response1</span><span class="o">=</span><span class="s">.*Event Start Test5.1 -&gt; loop on receive until message includes requestEnd = yes -&gt;</span>
+ <span class="err">received</span> <span class="err">message</span> <span class="err">-&gt</span><span class="c">; process complete.*</span>
</pre></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 31 16:11:00 2012
@@ -28,7 +28,7 @@
<li class="">
<a href="/getting-ode.html">Getting ODE</a>
</li>
- <li class=" dropdown">
+ <li class="active dropdown">
<a href="/user-guide.html" class="dropdown-toggle" data-toggle="dropdown" data-target="#">Documentation<b class="caret"></b></a>
<ul class="dropdown-menu">
<li><a href="/userguide/">User Guide</a></li>
@@ -85,7 +85,33 @@
<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">Only in 1.3.2</h4></div>
+<div class="toc">
+<ul>
+<li><a href="#how-to-use-ws-security-in-ode">How to use WS-Security in ODE?</a><ul>
+<li><a href="#quick-rampart-introduction">Quick Rampart introduction</a></li>
+<li><a href="#how-to-invoke-a-secure-web-service">How to invoke a secure web service?</a><ul>
+<li><a href="#prepare-your-service-document">Prepare your service document</a></li>
+<li><a href="#add-resources-to-ode-webapp-classpath">Add resources to ODE webapp classpath</a></li>
+<li><a href="#an-alternative-for-ws-security-policies">An alternative for WS-Security Policies</a></li>
+</ul>
+</li>
+<li><a href="#how-to-secure-the-web-service-exposed-by-a-process">How to secure the web service exposed by a process?</a></li>
+<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>
+<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>
+<li><a href="#the-nitty-gritty-details">the nitty-gritty details</a></li>
+</ul>
+</li>
+</ul>
+</li>
+</ul>
+</li>
+</ul>
+</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>
@@ -197,8 +223,8 @@
</ul>
<!-- let markdown notice that the list block is finished -->
-<div class="codehilite"><pre>alias.sample03-ns=http://sample03.policy.samples.rampart.apache.org
-sample03-ns.sample03-policy.ode.security.policy.file=mypolicy.xml
+<div class="codehilite"><pre><span class="na">alias.sample03-ns</span><span class="o">=</span><span class="s">http://sample03.policy.samples.rampart.apache.org</span>
+<span class="na">sample03-ns.sample03-policy.ode.security.policy.file</span><span class="o">=</span><span class="s">mypolicy.xml</span>
</pre></div>