Author: buildbot
Date: Mon Dec 31 11:34:45 2012
New Revision: 844394
Log:
Staging update by buildbot for ode
Modified:
websites/staging/ode/trunk/content/ (props changed)
websites/staging/ode/trunk/content/extensions/process-contexts.html
Propchange: websites/staging/ode/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Dec 31 11:34:45 2012
@@ -1 +1 @@
-1427078
+1427086
Modified: websites/staging/ode/trunk/content/extensions/process-contexts.html
==============================================================================
--- websites/staging/ode/trunk/content/extensions/process-contexts.html
(original)
+++ websites/staging/ode/trunk/content/extensions/process-contexts.html Mon Dec
31 11:34:45 2012
@@ -105,11 +105,11 @@ Whenever a message arrives through ODE's
For outgoing messages, <invoke> activities can be configured to take context
data from a (different) partner link, pass it again through a <em>context
interceptor</em> which translates the data back to transport-specific metadata.
Such propagation configuration can be defined per invoke activity in the
process model or on a global level in the deployment descriptor.
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.</p>
-<p><a name="ProcessContexts-{anchor:contexts}Contexts"></a></p>
-<h3 id="anchorcontextscontexts">{anchor:contexts}Contexts</h3>
-<p>Contexts are modeled as a bag of metadata information represented as
key-value pairs <code>(string, string)</code> 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.</p>
+<p><a name="ProcessContexts-Contexts"></a></p>
+<h3 id="contexts">Contexts</h3>
+<p>Contexts are modeled as a bag of metadata information represented as
key-value pairs <em>(string, string)</em> 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.</p>
<p>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 <a
href="http://svn.apache.org/viewvc/ode/trunk/bpel-schemas/src/main/xsd/contexts.xsd?view=markup";>here</a></p>
-<div class="caption">"Example: Context data in its XML representation"</div>
+<div class="caption">Example: Context data in its XML representation</div>
<div class="codehilite"><pre><span class="cp"><?xml version="1.0"
encoding="UTF-8"?></span>
<span class="nt"><ctx:contexts</span> <span
class="na">xmlns:ctx=</span><span
class="s">"http://www.apache.org/ode/schemas/context/2009"</span>
<span class="na">xmlns:xsi=</span><span
class="s">"http://www.w3.org/2001/XMLSchema-instance"</span> <span
class="na">xsi:schemaLocation=</span><span
class="s">"http://www.apache.org/ode/schemas/context/2009 contexts.xsd
"</span><span class="nt">></span>
@@ -235,7 +235,6 @@ ode-jbi.context.interceptors = my.full.q
<span class="nt"><ctx:propagate</span> <span
class="na">ctx:fromPartnerLink=</span><span
class="s">"testPartnerLink"</span> <span
class="na">ctx:context=</span><span class="s">"*"</span><span
class="nt">/></span>
<span class="nt"></bpel:invoke></span>
-:::xml
<span class="nt"><bpel:reply</span> <span class="err">...</span><span
class="nt">></span>
<span class="nt"><ctx:propagate</span> <span
class="na">ctx:fromPartnerLink=</span><span
class="s">"testPartnerLink"</span> <span
class="na">ctx:context=</span><span class="s">"*"</span><span
class="nt">/></span>
<span class="nt"></bpel:reply></span>
@@ -254,7 +253,7 @@ ode-jbi.context.interceptors = my.full.q
<p><a name="ProcessContexts-AccessingandAssigningContextData"></a></p>
<h4 id="accessing-and-assigning-context-data">Accessing and Assigning Context
Data</h4>
<p>Context data should be accessible within BPEL processes and from the
outside, e.g. for management purposes. For the former, the
<code><assign></code> activity has been extended to support copying data
from and to contexts of a partner link. The according
<code>from</code>/<code>to</code> specs are defined as follows:</p>
-<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>
<div class="codehilite"><pre><span class="nt"><assign></span>
<span class="c"><!-- copy 'tracing' and 'security'
contexts to a variable. --></span>
@@ -300,7 +299,7 @@ ode-jbi.context.interceptors = my.full.q
</div>
<p>When assigning context data to variables, the variable should be declared
to be an instance of the context XSD (see <a href="#contexts.html">Contexts
section</a>). It is also possible to copy only fragments of a context data set
by applying an XPath query to the <code>from</code>-spec:</p>
-<div class="caption">"Applying XPath-query to context data"</div>
+<div class="caption">Applying XPath-query to context data</div>
<div class="codehilite"><pre><span class="nt"><assign></span>
<span class="c"><!-- copy tracing id to a string variable. --></span>
