You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@ode.apache.org by va...@apache.org on 2012/12/31 17:10:55 UTC
svn commit: r1427159 - in /ode/site/trunk/content:
http-authentication.mdtext use-assign-to-build-messages.mdtext
writing-bpel-test-cases.mdtext ws-security-in-ode.mdtext
Author: vanto
Date: Mon Dec 31 16:10:54 2012
New Revision: 1427159
URL: http://svn.apache.org/viewvc?rev=1427159&view=rev
Log:
formatting tweaks.
Modified:
ode/site/trunk/content/http-authentication.mdtext
ode/site/trunk/content/use-assign-to-build-messages.mdtext
ode/site/trunk/content/writing-bpel-test-cases.mdtext
ode/site/trunk/content/ws-security-in-ode.mdtext
Modified: ode/site/trunk/content/http-authentication.mdtext
URL: http://svn.apache.org/viewvc/ode/site/trunk/content/http-authentication.mdtext?rev=1427159&r1=1427158&r2=1427159&view=diff
==============================================================================
--- ode/site/trunk/content/http-authentication.mdtext (original)
+++ ode/site/trunk/content/http-authentication.mdtext Mon Dec 31 16:10:54 2012
@@ -88,6 +88,4 @@ The schema of the `authenticate` element
</xs:schema>
-
- You can add this schema to your project to allow tools to display/validate the correct element structure.
-
+You can add this schema to your project to allow tools to display/validate the correct element structure.
Modified: ode/site/trunk/content/use-assign-to-build-messages.mdtext
URL: http://svn.apache.org/viewvc/ode/site/trunk/content/use-assign-to-build-messages.mdtext?rev=1427159&r1=1427158&r2=1427159&view=diff
==============================================================================
--- ode/site/trunk/content/use-assign-to-build-messages.mdtext (original)
+++ ode/site/trunk/content/use-assign-to-build-messages.mdtext Mon Dec 31 16:10:54 2012
@@ -1,4 +1,5 @@
Title: Use Assign to build messages
+Category: documentation
<a name="UseAssigntobuildmessages-UseAssigntobuildwholemessageatonce(allparts)"></a>
## Use Assign to build whole message at once (all parts)
Modified: ode/site/trunk/content/writing-bpel-test-cases.mdtext
URL: http://svn.apache.org/viewvc/ode/site/trunk/content/writing-bpel-test-cases.mdtext?rev=1427159&r1=1427158&r2=1427159&view=diff
==============================================================================
--- ode/site/trunk/content/writing-bpel-test-cases.mdtext (original)
+++ ode/site/trunk/content/writing-bpel-test-cases.mdtext Mon Dec 31 16:10:54 2012
@@ -1,4 +1,5 @@
Title: Writing BPEL Test Cases
+Category: documentation
## Overview
@@ -23,7 +24,7 @@ So to begin with your test process must
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:
- :::text
+ :::properties
namespace=http://ode/bpel/unit-test.wsdl
service=HelloService
operation=hello
@@ -38,7 +39,7 @@ A test descriptor can contain more that
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:
- :::text
+ :::properties
test1.properties
namespace=http://ode/bpel/unit-test/testCorrelation.wsdl
@@ -50,7 +51,7 @@ Also if your process needs to receive se
<!-- -->
- :::text
+ :::properties
test2.properties
namespace=http://ode/bpel/unit-test/testCorrelation.wsdl
@@ -64,8 +65,7 @@ Also if your process needs to receive se
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:
-
- :::text
+ :::properties
response1=ASYNC
@@ -147,7 +147,7 @@ The first assign initializes the probe p
The returned data is finally tested by using a nice regular expression for the response:
- :::text
+ :::properties
response1=.*Event Start Test5.1 -> loop on receive until message includes requestEnd = yes ->
received message -> process complete.*
Modified: ode/site/trunk/content/ws-security-in-ode.mdtext
URL: http://svn.apache.org/viewvc/ode/site/trunk/content/ws-security-in-ode.mdtext?rev=1427159&r1=1427158&r2=1427159&view=diff
==============================================================================
--- ode/site/trunk/content/ws-security-in-ode.mdtext (original)
+++ ode/site/trunk/content/ws-security-in-ode.mdtext Mon Dec 31 16:10:54 2012
@@ -1,8 +1,12 @@
Title: WS-Security in ODE
+Category: documentation
+
<a name="WS-SecurityinODE-HowtouseWS-SecurityinODE?"></a>
## How to use WS-Security in ODE?
-<div class="alert alert-warning"><h4 class="alert-heading">Only in 1.3.2</h4></div>
+[TOC]
+
+<div class="alert alert-warning"><h4 class="alert-heading">Only in 1.3.2+</h4></div>
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.
@@ -123,7 +127,7 @@ To do so:
<!-- let markdown notice that the list block is finished -->
- :::xml
+ :::properties
alias.sample03-ns=http://sample03.policy.samples.rampart.apache.org
sample03-ns.sample03-policy.ode.security.policy.file=mypolicy.xml
@@ -149,7 +153,7 @@ No. ODE comes with the following Axis2 m
##### How to run them
- :::xml
+ :::text
$ cd axis2-war
$ buildr test:Secure