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 11:53:46 UTC
svn commit: r1427078 -
/ode/site/trunk/content/extensions/process-contexts.mdtext
Author: vanto
Date: Mon Dec 31 10:53:46 2012
New Revision: 1427078
URL: http://svn.apache.org/viewvc?rev=1427078&view=rev
Log:
fix formatting.
Modified:
ode/site/trunk/content/extensions/process-contexts.mdtext
Modified: ode/site/trunk/content/extensions/process-contexts.mdtext
URL: http://svn.apache.org/viewvc/ode/site/trunk/content/extensions/process-contexts.mdtext?rev=1427078&r1=1427077&r2=1427078&view=diff
==============================================================================
--- ode/site/trunk/content/extensions/process-contexts.mdtext (original)
+++ ode/site/trunk/content/extensions/process-contexts.mdtext Mon Dec 31 10:53:46 2012
@@ -1,4 +1,6 @@
Title: Process Contexts
+Category: documentation
+
<a name="ProcessContexts-ProcessContexts"></a>
## Process Contexts
@@ -32,7 +34,9 @@ Contexts are modeled as a bag of metadat
Since contexts should also be accessible in BPEL, there is also an XML-based representation. It is defined as follows, the according XMLSchema can be found [here](http://svn.apache.org/viewvc/ode/trunk/bpel-schemas/src/main/xsd/contexts.xsd?view=markup)
-<DIV class="code panel" style="border-style: solid;border-width: 1px;"><DIV class="codeHeader panelHeader" style="border-bottom-width: 1px;border-bottom-style: solid;"><B>"Example: Context data in its XML representation"</B></DIV><DIV class="codeContent panelContent">
+<div class="caption">"Example: Context data in its XML representation"</div>
+
+ :::xml
<?xml version="1.0" encoding="UTF-8"?>
<ctx:contexts xmlns:ctx="http://www.apache.org/ode/schemas/context/2009" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.apache.org/ode/schemas/context/2009 contexts.xsd ">
<ctx:context name="foo">
@@ -49,7 +53,7 @@ Since contexts should also be accessible
At the transport level, message headers can be translated to context data and contexts can be translated to message headers. Context interceptors define how the headers are set to/from contexts and which contexts are affected. Interceptors are Java classes that implement the following interface. They can be registered either globally in ode's property configuration file or per process in the `deploy.xml`.
-
+ :::java
/**
* Context Interceptors can map message headers (or even payload) to
* context information that is attached to process models.
@@ -79,7 +83,7 @@ At the transport level, message headers
There is also a more high-level interface defined in terms of an abstract class:
-
+ :::java
public abstract class AbstractContextInterceptor implements ContextInterceptor {
public abstract void configure(Element configuration);
@@ -99,7 +103,6 @@ There is also a more high-level interfac
}
-
<a name="ProcessContexts-WorkingwithContextsinBPEL"></a>
### Working with Contexts in BPEL
@@ -112,13 +115,17 @@ In order to use context interceptors, th
Engine-wide context interceptors are registered in ODE's properties file (either `ode-axis2.properties` or `ode-jbi.properties`) using the properties key `context.interceptors`.
-<DIV class="code panel" style="border-style: solid;border-width: 1px;"><DIV class="codeHeader panelHeader" style="border-bottom-width: 1px;border-bottom-style: solid;"><B>ode-axis2.properties</B></DIV><DIV class="codeContent panelContent">
+<div class="caption">ode-axis2.properties</div>
+
+ :::text
...
ode-axis2.context.interceptors = my.full.qualified.context.interceptor.class.name
...
-<DIV class="code panel" style="border-style: solid;border-width: 1px;"><DIV class="codeHeader panelHeader" style="border-bottom-width: 1px;border-bottom-style: solid;"><B>ode-jbi.properties</B></DIV><DIV class="codeContent panelContent">
+<div class="caption">ode-jbi.properties</div>
+
+ :::text
...
ode-jbi.context.interceptors = my.full.qualified.context.interceptor.class.name
...
@@ -126,7 +133,7 @@ Engine-wide context interceptors are reg
Per-process context interceptors are declared in ODE's deployment descriptor deploy.xml:
-<DIV class="code panel" style="border-style: solid;border-width: 1px;"><DIV class="codeHeader panelHeader" style="border-bottom-width: 1px;border-bottom-style: solid;"><B>deploy.xml</B></DIV><DIV class="codeContent panelContent">
+<div class="caption">deploy.xml</div>
<deploy xmlns="http://www.apache.org/ode/schemas/dd/2007/03"
xmlns:pns="http://ode/bpel/unit-test"
xmlns:wns="http://ode/bpel/unit-test.wsdl">
@@ -159,13 +166,13 @@ Static propagation rules can be configur
In addition to static propagation rules, context propagation can be explicitly configured for outbound interaction activities (i.e. `<invoke>` and `<reply>`. Therefore, we introduce a new BPEL extension element `<ctx:propagate>` in the `[http://ode.apache.org/contextPropagation](http://ode.apache.org/contextPropagation)` namespace (to which the `ctx`\-prefix is bound to), following the syntax as described below:
-
+ :::xml
<bpel:invoke ...>
<ctx:propagate ctx:fromPartnerLink="testPartnerLink" ctx:context="*"/>
</bpel:invoke>
-
+ :::xml
<bpel:reply ...>
<ctx:propagate ctx:fromPartnerLink="testPartnerLink" ctx:context="*"/>
</bpel:reply>
@@ -185,7 +192,9 @@ The context data identified by this prop
Context data should be accessible within BPEL processes and from the outside, e.g. for management purposes. For the former, the `<assign>` activity has been extended to support copying data from and to contexts of a partner link. The according `from`/`to` specs are defined as follows:
-<DIV class="code panel" style="border-style: solid;border-width: 1px;"><DIV class="codeHeader panelHeader" style="border-bottom-width: 1px;border-bottom-style: solid;"><B>"from/to specs for the work with context data"</B></DIV><DIV class="codeContent panelContent">
+<div class="caption">"from/to specs for the work with context data"</div>
+
+ :::xml
<assign>
<!-- copy 'tracing' and 'security' contexts to a variable. -->
<copy>
@@ -222,14 +231,16 @@ Context data should be accessible within
<div class="alert alert-info">
- - `context="*"` in `from`\-specs selects all contexts.
- - `context="*"` in `to`\-specs replaces existing contexts with context data selected by the `from`\-spec.
- - `context="+"` in `to`\-specs merges existing contexts with context data selected by the `from`\-spec.
+ <ul>
+ <li><code>context="*"</code> in <code>from</code>-specs selects all contexts.</li>
+ <li><code>context="*"</code> in <code>to</code>-specs replaces existing contexts with context data selected by the <code>from</code>-spec.</li>
+ <li><code>context="+"</code> in <code>to</code>-specs merges existing contexts with context data selected by the <code>from</code>-spec.</li>
+ <ul>
</div>
When assigning context data to variables, the variable should be declared to be an instance of the context XSD (see [Contexts section](#contexts.html)). It is also possible to copy only fragments of a context data set by applying an XPath query to the `from`\-spec:
-<DIV class="code panel" style="border-style: solid;border-width: 1px;"><DIV class="codeHeader panelHeader" style="border-bottom-width: 1px;border-bottom-style: solid;"><B>"Applying XPath-query to context data"</B></DIV><DIV class="codeContent panelContent">
+<div class="caption">"Applying XPath-query to context data"</div>
<assign>
<!-- copy tracing id to a string variable. -->
<copy>