Author: vanto
Date: Mon Dec 31 11:34:41 2012
New Revision: 1427086
URL: http://svn.apache.org/viewvc?rev=1427086&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=1427086&r1=1427085&r2=1427086&view=diff
==============================================================================
--- ode/site/trunk/content/extensions/process-contexts.mdtext (original)
+++ ode/site/trunk/content/extensions/process-contexts.mdtext Mon Dec 31
11:34:41 2012
@@ -27,14 +27,14 @@ For outgoing messages, <invoke> activiti
Context data can be assigned to variables. Therefore, the context data is
translated into XML data, following a predefined schema. It is possible to
define which contexts of a partner link are copied to a variable. Similarly,
context data can be copied from a variable back into the context of a certain
partner link.
Contexts can be used to classify or tag process instances and it is useful to
make this information accessible for process management tools. Hence, this
specification extends the process management API to make context data queryable
and accessible.
-<a name="ProcessContexts-{anchor:contexts}Contexts"></a>
-### {anchor:contexts}Contexts
+<a name="ProcessContexts-Contexts"></a>
+### Contexts
-Contexts are modeled as a bag of metadata information represented as key-value
pairs `(string, string)` and are attached to partner links. Contexts have a
name attribute. Contexts are persisted in ODE's runtime database. Long values
are stored as a CLOB whereas shorter values (< 250 characters) are
automatically stored in an indexed VARCHAR field.
+Contexts are modeled as a bag of metadata information represented as key-value
pairs *(string, string)* and are attached to partner links. Contexts have a
name attribute. Contexts are persisted in ODE's runtime database. Long values
are stored as a CLOB whereas shorter values (< 250 characters) are
automatically stored in an indexed VARCHAR field.
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="caption">"Example: Context data in its XML representation"</div>
+<div class="caption">Example: Context data in its XML representation</div>
:::xml
<?xml version="1.0" encoding="UTF-8"?>
@@ -171,8 +171,6 @@ In addition to static propagation rules,
<ctx:propagate ctx:fromPartnerLink="testPartnerLink" ctx:context="*"/>
</bpel:invoke>
-
- :::xml
<bpel:reply ...>
<ctx:propagate ctx:fromPartnerLink="testPartnerLink" ctx:context="*"/>
</bpel:reply>
@@ -192,7 +190,7 @@ 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="caption">"from/to specs for the work with context data"</div>
+<div class="caption">from/to specs for the work with context data</div>
:::xml
<assign>
@@ -240,7 +238,7 @@ Context data should be accessible within
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="caption">"Applying XPath-query to context data"</div>
+<div class="caption">Applying XPath-query to context data</div>
<assign>
<!-- copy tracing id to a string variable. -->
<copy>
