Author: buildbot
Date: Wed Dec 5 20:02:20 2012
New Revision: 840851
Log:
Staging update by buildbot for ode
Modified:
websites/staging/ode/trunk/content/ (props changed)
websites/staging/ode/trunk/content/architectural-overview.html
websites/staging/ode/trunk/content/contributors.html
websites/staging/ode/trunk/content/copy-with-insert-attribute.html
websites/staging/ode/trunk/content/creating-a-process.html
websites/staging/ode/trunk/content/direct-process-to-process-communication.html
websites/staging/ode/trunk/content/eclipse-ide.html
websites/staging/ode/trunk/content/external-variables.html
websites/staging/ode/trunk/content/http-authentication.html
websites/staging/ode/trunk/content/instance-data-cleanup.html
websites/staging/ode/trunk/content/jbi-deployment.html
websites/staging/ode/trunk/content/management-api.html
websites/staging/ode/trunk/content/ode-execution-events.html
websites/staging/ode/trunk/content/process-versioning.html
websites/staging/ode/trunk/content/restful-bpel-part-i.html
websites/staging/ode/trunk/content/restful-bpel-part-ii.html
websites/staging/ode/trunk/content/roadmap.html
websites/staging/ode/trunk/content/sitemap.html
websites/staging/ode/trunk/content/source-code.html
websites/staging/ode/trunk/content/user-guide.html
websites/staging/ode/trunk/content/using-a-jndi-datasource-under-servicemix-jbi.html
websites/staging/ode/trunk/content/war-deployment.html
websites/staging/ode/trunk/content/ws-bpel-20-specification-compliance.html
websites/staging/ode/trunk/content/xquery-extensions.html
Propchange: websites/staging/ode/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Dec 5 20:02:20 2012
@@ -1 +1 @@
-1417608
+1417613
Modified: websites/staging/ode/trunk/content/architectural-overview.html
==============================================================================
--- websites/staging/ode/trunk/content/architectural-overview.html (original)
+++ websites/staging/ode/trunk/content/architectural-overview.html Wed Dec 5
20:02:20 2012
@@ -90,7 +90,7 @@
<p><a name="ArchitecturalOverview-Components"></a></p>
<h2 id="components">Components</h2>
<p>The key components of the ODE architecture include the ODE BPEL Compiler,
ODE BPEL Engine Runtime, ODE Data Access Objects (DAOs), ODE Integration Layers
(ILs), and user tooling. A high-level depiction of the relationships between
these components is shown in the Figure below. It can be summarized as: "The
compiler converts BPEL documents into a form executable by the run-time, which
executes them in a reliable fashion by relying on a persistent store accessible
via the DAOs; the run-time executes in the context of an Integration Layer
which connects the engine to the broader execution environment ( i.e. the
"world").</p>
-<p><img alt="ODE Architecture" src="/img/OdeArchitecture.png" /></p>
+<p><img alt="ODE Architecture" src="/img/ODEArchitecture.png" /></p>
<p><a name="ArchitecturalOverview-ODEBPELCompiler"></a></p>
<h3 id="ode-bpel-compiler">ODE BPEL Compiler</h3>
<p>The BPEL compiler is responsible for the conversion of the source BPEL
artifacts (i.e. BPEL process documents, WSDLs, and schemas) into a compiled
representation suitable for execution. The output of the compiler is either a
"good" compiled representation, or a list of error messages indicating problems
with the source artefacts.</p>
Modified: websites/staging/ode/trunk/content/contributors.html
==============================================================================
--- websites/staging/ode/trunk/content/contributors.html (original)
+++ websites/staging/ode/trunk/content/contributors.html Wed Dec 5 20:02:20
2012
@@ -83,7 +83,7 @@
<div class="span12">
<p><a name="Contributors-Committers"></a></p>
<h2 id="committers">Committers</h2>
-<p>Here is the list of people who are actively working and committing on
Ode.</p>
+<p>Here is the list of people who are actively working and committing on
ODE.</p>
<table class="table table-striped">
<thead>
<tr>
@@ -182,7 +182,7 @@
<p><a name="Contributors-Sponsors"></a></p>
<h2 id="sponsors">Sponsors</h2>
-<p><a href="http://www.yourkit.com/";>YourKit</a> has graciously provided
YourKit Java Profiler licenses to support our performance and quality efforts.
We've had a wonderful experience using their tool – we were able to
quickly and accurately find the cause of some issues in Ode -- and definitely
recommend using it while building your own software.</p>
+<p><a href="http://www.yourkit.com/";>YourKit</a> has graciously provided
YourKit Java Profiler licenses to support our performance and quality efforts.
We've had a wonderful experience using their tool – we were able to
quickly and accurately find the cause of some issues in ODE -- and definitely
recommend using it while building your own software.</p>
</div>
</div>
Modified: websites/staging/ode/trunk/content/copy-with-insert-attribute.html
==============================================================================
--- websites/staging/ode/trunk/content/copy-with-insert-attribute.html
(original)
+++ websites/staging/ode/trunk/content/copy-with-insert-attribute.html Wed Dec
5 20:02:20 2012
@@ -84,7 +84,7 @@
<p><a
name="copywithinsertattribute-<bpel:copy>withinsertattribute"></a></p>
<h2 id="wzxhzdk13-with-insert-attribute"><bpel:copy> with insert attribute</h2>
<div class="alert alert-warning">
- This is a proposal for a BPEL extension (non-standard); This proposal is
not yet implemented in Ode. See http://issues.apache.org/jira/browse/ODE-145
for current status information.
+ This is a proposal for a BPEL extension (non-standard); This proposal is
not yet implemented in ODE. See http://issues.apache.org/jira/browse/ODE-145
for current status information.
</div>
<p>Consider a simple use case. A BPEL process collects quotes from a number of
suppliers, to determine which one provides the best price, before submitting an
order to that supplier. Typically this will be done using the <bpel:foreach>
activity, collecting information from each quote into a variable, and later on
extracting a specific node from that variable, e.g. using XPath predicate to
select the supplier with the lowest price.</p>
Modified: websites/staging/ode/trunk/content/creating-a-process.html
==============================================================================
--- websites/staging/ode/trunk/content/creating-a-process.html (original)
+++ websites/staging/ode/trunk/content/creating-a-process.html Wed Dec 5
20:02:20 2012
@@ -83,7 +83,7 @@
<div class="span12">
<div class="toc">
<ul>
-<li><a href="#deploying-a-process-in-ode">Deploying a Process in Ode</a></li>
+<li><a href="#deploying-a-process-in-ode">Deploying a Process in ODE</a></li>
<li><a href="#deployment-descriptor">Deployment Descriptor</a></li>
<li><a href="#formal-definition">Formal definition</a><ul>
<li><a href="#examples">Examples</a></li>
@@ -97,13 +97,13 @@
</ul>
</div>
<p><a name="CreatingaProcess-DeployingaProcessinOde"></a></p>
-<h3 id="deploying-a-process-in-ode">Deploying a Process in Ode</h3>
+<h3 id="deploying-a-process-in-ode">Deploying a Process in ODE</h3>
<p>Each deployment is a directory with all relevant deployment artifacts. At
the minimum it will contain the deployment descriptor, one or more process
definitions (BPEL or .cbp), WSDL and XSDs (excluding those compiled into the
.cbp). It may also contain other files, such as SVGs or XSLs. The deployment
descriptor is a file named deploy.xml (see the next paragraoh for its
description).</p>
<p>During deployment, the process engine loads all documents from the
deployment descriptor. Loading documents allow it to reference processes,
service and schema definitions using fully qualified names, and import based on
namespaces instead of locations.</p>
-<p>To deploy in Ode, just copy the whole directory containing your artifacts
(the directory itself, not only its content) in the path
%DEPLOYMENT_ROOT%/WEB-INF/processes (in Tomcat it would be
%TOMCAT_HOME%/webapps/ode/WEB-INF/processes).</p>
+<p>To deploy in ODE, just copy the whole directory containing your artifacts
(the directory itself, not only its content) in the path
%DEPLOYMENT_ROOT%/WEB-INF/processes (in Tomcat it would be
%TOMCAT_HOME%/webapps/ode/WEB-INF/processes).</p>
<p><a name="CreatingaProcess-DeploymentDescriptor"></a></p>
<h3 id="deployment-descriptor">Deployment Descriptor</h3>
-<p>To deploy your process in Ode you will need to create a simple deployment
descriptor with basic information. The deploy.xml file configures one or
several processes to use specific services. For each process, deploy.xml must
supply binding information for partner links to concrete WSDL services. Every
partner link used with a <receive> activity must be matched with a <provide>
element, and every partnerLink used in an <invoke> activity must be matched
with an <invoke> element in <em>deploy.xml</em> (unless that partnerLink has
initializePartnerRole="false").</p>
+<p>To deploy your process in ODE you will need to create a simple deployment
descriptor with basic information. The deploy.xml file configures one or
several processes to use specific services. For each process, deploy.xml must
supply binding information for partner links to concrete WSDL services. Every
partner link used with a <receive> activity must be matched with a <provide>
element, and every partnerLink used in an <invoke> activity must be matched
with an <invoke> element in <em>deploy.xml</em> (unless that partnerLink has
initializePartnerRole="false").</p>
<p><a name="CreatingaProcess-Formaldefinition"></a></p>
<h3 id="formal-definition">Formal definition</h3>
<p>The XML schema describing ODE's deployment descriptor is available <a
href="http://svn.apache.org/viewvc/ode/trunk/bpel-schemas/src/main/xsd/dd.xsd?view=markup";>here</a>.
The root element, deploy, contains a list of all deployed processes from the
deployment directory:</p>
@@ -182,7 +182,7 @@
<h4 id="additional-settings">Additional settings</h4>
<p><a name="CreatingaProcess-Inmemoryexecution"></a></p>
<h5 id="in-memory-execution">In memory execution</h5>
-<p>For performance purposes, you can define a process as being executed only
in-memory. This greatly reduces the amount of generated queries and puts far
less load on your database. Both persistent and non-persistent processes can
cohabit in Ode.</p>
+<p>For performance purposes, you can define a process as being executed only
in-memory. This greatly reduces the amount of generated queries and puts far
less load on your database. Both persistent and non-persistent processes can
cohabit in ODE.</p>
<p>To declare a process as in-memory just add an in-memory element in your
deploy.xml:</p>
<div class="codehilite"><pre><span class="nt"><process</span> <span
class="na">name=</span><span class="s">"pns:HelloWorld2"</span><span
class="nt">></span>
<span class="nt"><in-memory></span>true<span
class="nt"></in-memory></span>
Modified:
websites/staging/ode/trunk/content/direct-process-to-process-communication.html
==============================================================================
---
websites/staging/ode/trunk/content/direct-process-to-process-communication.html
(original)
+++
websites/staging/ode/trunk/content/direct-process-to-process-communication.html
Wed Dec 5 20:02:20 2012
@@ -81,7 +81,7 @@
<div class="row">
<div class="span12">
- <p>Ode automatically optimizes all process-to-process communication
such that all message exchanges happen directly inside the engine and do not go
through the integration layer (e.g. Axis2, JBI, ...).</p>
+ <p>ODE automatically optimizes all process-to-process communication
such that all message exchanges happen directly inside the engine and do not go
through the integration layer (e.g. Axis2, JBI, ...).</p>
</div>
</div>
Modified: websites/staging/ode/trunk/content/eclipse-ide.html
==============================================================================
--- websites/staging/ode/trunk/content/eclipse-ide.html (original)
+++ websites/staging/ode/trunk/content/eclipse-ide.html Wed Dec 5 20:02:20 2012
@@ -82,7 +82,7 @@
<div class="row">
<div class="span12">
<p><a name="EclipseIDE-DevelopingOdewiththeEclipseIDE"></a></p>
-<h2 id="developing-ode-with-the-eclipse-ide">Developing Ode with the Eclipse
IDE</h2>
+<h2 id="developing-ode-with-the-eclipse-ide">Developing ODE with the Eclipse
IDE</h2>
<p>First, be sure to read <a href="building-ode.html">Building ODE</a> to
learn how to install Ruby, Rake and Buildr.</p>
<p><a name="EclipseIDE-1.BuildOde"></a></p>
<h3 id="1-build-ode">1. Build ODE</h3>
Modified: websites/staging/ode/trunk/content/external-variables.html
==============================================================================
--- websites/staging/ode/trunk/content/external-variables.html (original)
+++ websites/staging/ode/trunk/content/external-variables.html Wed Dec 5
20:02:20 2012
@@ -93,7 +93,7 @@
<p><a
name="ExternalVariables-DeclaringExternalVariablesintheProcessDefinition"></a></p>
<h3 id="declaring-external-variables-in-the-process-definition">Declaring
External Variables in the Process Definition</h3>
<div class="alert alert-warning">
- External variables are only available on Ode 1.2+
+ External variables are only available on ODE 1.2+
</div>
<p>Syntax:</p>
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 Wed Dec 5
20:02:20 2012
@@ -84,7 +84,7 @@
<p>This section explains how to perform authentication against Web
services requiring HTTP basic, digest or NTLM authentication mechanisms.<br />
</p>
<div class="alert alert-warning"><h4 class="alert-heading">Non-Standard</h4>
- This mode of authentication is non-standard in the Web service world
because the authentication data is passed outside of the SOAP message. This
feature is still experimental and requires Ode >1.1
+ This mode of authentication is non-standard in the Web service world
because the authentication data is passed outside of the SOAP message. This
feature is still experimental and requires ODE >1.1
</div>
<p><a name="HTTPAuthentication-Authenticationelementandmessagepart"></a></p>
Modified: websites/staging/ode/trunk/content/instance-data-cleanup.html
==============================================================================
--- websites/staging/ode/trunk/content/instance-data-cleanup.html (original)
+++ websites/staging/ode/trunk/content/instance-data-cleanup.html Wed Dec 5
20:02:20 2012
@@ -89,7 +89,7 @@
<p><a name="InstanceDataCleanup-Cleanuponcompletion"></a></p>
<h3 id="cleanup-on-completion">Cleanup on completion</h3>
<p>{panel}
-This feature is only available in Ode 1.3 or later
+This feature is only available in ODE 1.3 or later
{panel}</p>
<p>The easiest approach to get started is simply to wait until the instance
execution is finished and then cleanup everything that's related to it. That
would include the instance state with its variables, scopes and correlation,
but also all the messages it has received and sent. Execution events should
also be disposed of. So this description defines 5 different categories:
instance, messages and events. We should be able to turn on and off each level
separately.</p>
<ul>
Modified: websites/staging/ode/trunk/content/jbi-deployment.html
==============================================================================
--- websites/staging/ode/trunk/content/jbi-deployment.html (original)
+++ websites/staging/ode/trunk/content/jbi-deployment.html Wed Dec 5 20:02:20
2012
@@ -123,7 +123,7 @@
<span class="n">export</span> <span class="n">ODE_HOME</span><span
class="o">=</span><span class="sr">/path/</span><span class="n">to</span><span
class="sr">/ode/</span><span class="n">distribution</span>
<span class="c1"># On Windows</span>
-<span class="n">set</span> <span class="n">ODE_HOME</span><span
class="o">=</span><span class="n">C:</span><span class="o">\</span><span
class="n">Path</span><span class="o">\</span><span class="n">To</span><span
class="o">\</span><span class="n">Ode</span><span class="o">\</span><span
class="n">Distribution</span>
+<span class="n">set</span> <span class="n">ODE_HOME</span><span
class="o">=</span><span class="n">C:</span><span class="o">\</span><span
class="n">Path</span><span class="o">\</span><span class="n">To</span><span
class="o">\</span><span class="n">ODE</span><span class="o">\</span><span
class="n">Distribution</span>
</pre></div>
Modified: websites/staging/ode/trunk/content/management-api.html
==============================================================================
--- websites/staging/ode/trunk/content/management-api.html (original)
+++ websites/staging/ode/trunk/content/management-api.html Wed Dec 5 20:02:20
2012
@@ -81,7 +81,7 @@
<div class="row">
<div class="span12">
- <p>Ode has a complete management API to check which processes are
deployed, running and completed instances, variables values and more. To see
which methods are available, have a look at the <a
href="http://ode.apache.org/javadoc/org/apache/ode/bpel/pmapi/ProcessManagement.html";>ProcessManagement</a>
and
[InstanceManagement|http://ode.apache.org/javadoc/org/apache/ode/bpel/pmapi/InstanceManagement.html]
interfaces, the javadoc is pretty comprehensive.</p>
+ <p>ODE has a complete management API to check which processes are
deployed, running and completed instances, variables values and more. To see
which methods are available, have a look at the <a
href="http://ode.apache.org/javadoc/org/apache/ode/bpel/pmapi/ProcessManagement.html";>ProcessManagement</a>
and
[InstanceManagement|http://ode.apache.org/javadoc/org/apache/ode/bpel/pmapi/InstanceManagement.html]
interfaces, the javadoc is pretty comprehensive.</p>
<p>These two interfaces are available as web services on the Axis2-based
distribution. The corresponding WSDL can be found <a
href="http://svn.apache.org/repos/asf/ode/trunk/axis2/src/main/wsdl/pmapi.wsdl";>here</a>.</p>
<p>To invoke these two services, any web service client should work (in a
perfect interoperable world). To ease the invocation when using an Axis2
client, a helper class is bundled in ode-axis2.jar: <a
href="http://ode.apache.org/javadoc/axis2/org/apache/ode/axis2/service/ServiceClientUtil.html";>ServiceClientUtil</a>.
Usage examples are also available in test classes
[InstanceManagementTest|http://svn.apache.org/repos/asf/ode/trunk/axis2/src/test/java/org/apache/ode/axis2/management/InstanceManagementTest.java]
and
[ProcessManagementTest|http://svn.apache.org/repos/asf/ode/trunk/axis2/src/test/java/org/apache/ode/axis2/management/ProcessManagementTest.java].
Here is a short example demonstrating the invocation of the
<em>listAllProcesses</em> operation:
{code:java}
Modified: websites/staging/ode/trunk/content/ode-execution-events.html
==============================================================================
--- websites/staging/ode/trunk/content/ode-execution-events.html (original)
+++ websites/staging/ode/trunk/content/ode-execution-events.html Wed Dec 5
20:02:20 2012
@@ -176,7 +176,7 @@
<p>The filter defined on a scope is automatically inherited by its inner
scopes. So if no filter is defined on a scope, it will use the settings of its
closest parent scope having event filters (up to the process). Note that what
gets inherited is the full list of selected events, not each event definition
individually.</p>
<p><a name="ODEExecutionEvents-Eventlisteners"></a></p>
<h3 id="event-listeners">Event listeners</h3>
-<p>Ode lets you register your own event listeners to analyze all produced
events and do whatever you want to do with them. To create a listener you just
need to implement the <a
href="https://svn.apache.org/repos/asf/ode/trunk/bpel-api/src/main/java/org/apache/ode/bpel/iapi/BpelEventListener.java";>org.apache.ode.bpel.iapi.BpelEventListener</a>
interface.</p>
+<p>ODE lets you register your own event listeners to analyze all produced
events and do whatever you want to do with them. To create a listener you just
need to implement the <a
href="https://svn.apache.org/repos/asf/ode/trunk/bpel-api/src/main/java/org/apache/ode/bpel/iapi/BpelEventListener.java";>org.apache.ode.bpel.iapi.BpelEventListener</a>
interface.</p>
<p>Then add your implementation in the server's classpath and add a property
in ode-axis2.properties giving your fully qualified implementation class name.
Something like:</p>
<div class="codehilite"><pre><span class="n">ode</span><span
class="o">-</span><span class="n">axis2</span><span class="o">.</span><span
class="n">event</span><span class="o">.</span><span
class="n">listeners</span><span class="o">=</span><span
class="n">com</span><span class="o">.</span><span class="n">compamy</span><span
class="o">.</span><span class="n">product</span><span class="o">.</span><span
class="n">MyOdeEventListener</span>
</pre></div>
Modified: websites/staging/ode/trunk/content/process-versioning.html
==============================================================================
--- websites/staging/ode/trunk/content/process-versioning.html (original)
+++ websites/staging/ode/trunk/content/process-versioning.html Wed Dec 5
20:02:20 2012
@@ -1,7 +1,7 @@
<!DOCTYPE html>
<html>
<head>
- <title>Process Versioning *
[Introduction](#ProcessVersioning-Introduction) * [How Versioning
Works](#ProcessVersioning-HowVersioningWorks) * [Process Versioning in
Ode](#ProcessVersioning-ProcessVersioninginOde) * [Remote Deployment vs.
Hand-Made
Deployment](#ProcessVersioning-RemoteDeploymentvs.Hand-MadeDeployment)</title>
+ <title>Process Versioning *
[Introduction](#ProcessVersioning-Introduction) * [How Versioning
Works](#ProcessVersioning-HowVersioningWorks) * [Process Versioning in
ODE](#ProcessVersioning-ProcessVersioninginOde) * [Remote Deployment vs.
Hand-Made
Deployment](#ProcessVersioning-RemoteDeploymentvs.Hand-MadeDeployment)</title>
<meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
<meta property="og:image" content="http://ode.apache.org/img/ode-logo.png";
/>
@@ -70,7 +70,7 @@
<header class="jumbotron subhead" id="overview">
<div class="container">
- <h1>Process Versioning *
[Introduction](#ProcessVersioning-Introduction) * [How Versioning
Works](#ProcessVersioning-HowVersioningWorks) * [Process Versioning in
Ode](#ProcessVersioning-ProcessVersioninginOde) * [Remote Deployment vs.
Hand-Made
Deployment](#ProcessVersioning-RemoteDeploymentvs.Hand-MadeDeployment)</h1>
+ <h1>Process Versioning *
[Introduction](#ProcessVersioning-Introduction) * [How Versioning
Works](#ProcessVersioning-HowVersioningWorks) * [Process Versioning in
ODE](#ProcessVersioning-ProcessVersioninginOde) * [Remote Deployment vs.
Hand-Made
Deployment](#ProcessVersioning-RemoteDeploymentvs.Hand-MadeDeployment)</h1>
</div>
</header>
@@ -83,22 +83,22 @@
<div class="span12">
<p><a name="ProcessVersioning-Introduction"></a></p>
<h3 id="introduction">Introduction</h3>
-<p>Before starting on what process versioning exactly does, let's see what the
world (or at least Ode) would be without versioning. It will be much more
easier for you to understand the solution after fully seeing the problem.</p>
-<p>So you're starting using Ode and you've just designed you first business
process. It's all nice and dandy and works perfectly. It works so well that you
let your users start using it. It's not really production but you know, release
early, release often, so let's see what users think of it. After a couple of
days you realize that a couple of steps are missing, you add them in your
process and once again, it executes smoothly. So let's see what our users think
of the improvement! Next thing you know, your phone starts ringing and the user
on the other side is most likely pretty upset. What happened?</p>
+<p>Before starting on what process versioning exactly does, let's see what the
world (or at least ODE) would be without versioning. It will be much more
easier for you to understand the solution after fully seeing the problem.</p>
+<p>So you're starting using ODE and you've just designed you first business
process. It's all nice and dandy and works perfectly. It works so well that you
let your users start using it. It's not really production but you know, release
early, release often, so let's see what users think of it. After a couple of
days you realize that a couple of steps are missing, you add them in your
process and once again, it executes smoothly. So let's see what our users think
of the improvement! Next thing you know, your phone starts ringing and the user
on the other side is most likely pretty upset. What happened?</p>
<p>So when you start using a process, executions for it are created, running
processes if you like (also called process instances). Depending on the type of
your business these could take a variable amount of time to execute but they're
usually not instantaneous. So you have all these running processes sometimes
doing things, sometimes just waiting there and all of a sudden, a brand new
process definition replaces the original one all these executions have been
using so far. What is a process engine to do with all these executions? Well,
the most logic thing on earth: just nuke them all.</p>
<p>At this time there's no simple automated way to migrate a running process
that has been executing using one definition to another new one. Computing the
differences between the 2 definitions can be very complex and chances are that
they're not even compatible! When you think of all these little tasks that are
arranged just so to guarantee a perfect execution using the right data types,
even minor alterations can get really tricky to apply on instances without
blowing them all.</p>
<p>So here is the crude and sad truth: without having some versioning goodness
in it, a process engine will always delete all the running instances when a new
process definition is deployed.</p>
<p><a name="ProcessVersioning-HowVersioningWorks"></a></p>
<h3 id="how-versioning-works">How Versioning Works</h3>
<p>So if existing executions can't be migrated, what are you going to do with
them? Well, just let them be. Versioning is based on the fact that, instead of
directly updating the original process definition (leaving its instances to
their dreadful fate), another new version of this definition is created. The
older one is declared retired so no new executions can be started on that one,
the new process is the one to be used now on. But running instances can still
finish their job peacefully as the process they've been using to execute so
far is still available and unchanged.</p>
-<p>However Ode also has the concept of deployment bundles and supports 2 modes
of deployment (remotely or manually directly on the filsesystem). Let's see how
we get versioning to work under those conditions.</p>
+<p>However ODE also has the concept of deployment bundles and supports 2 modes
of deployment (remotely or manually directly on the filsesystem). Let's see how
we get versioning to work under those conditions.</p>
<p><a name="ProcessVersioning-ProcessVersioninginOde"></a></p>
-<h4 id="process-versioning-in-ode">Process Versioning in Ode</h4>
-<p>In Ode, processes are deployed in what we call a deployment bundle. When
you come down to it, it's just a zip file or a directory containing Ode's
deployment descriptor (<a
href="creating-a-process#deployment-descriptor.html">deploy.xml</a>), the
processes BPEL and all the other goodies necessary for your BPEL to run (WSDLs,
schemas, xsl stylesheets, you name it). And what Ode is using to know you're
redeploying the same thing is the deployment bundle name.</p>
-<p>So when you're redeploying a deployment bundle in Ode, here is what
happens:</p>
+<h4 id="process-versioning-in-ode">Process Versioning in ODE</h4>
+<p>In ODE, processes are deployed in what we call a deployment bundle. When
you come down to it, it's just a zip file or a directory containing ODE's
deployment descriptor (<a
href="creating-a-process#deployment-descriptor.html">deploy.xml</a>), the
processes BPEL and all the other goodies necessary for your BPEL to run (WSDLs,
schemas, xsl stylesheets, you name it). And what ODE is using to know you're
redeploying the same thing is the deployment bundle name.</p>
+<p>So when you're redeploying a deployment bundle in ODE, here is what
happens:</p>
<ol>
<li>A new version is attributed to the bundle by incrementing the version
number of the last deployment.</li>
-<li>Ode checks whether the same bundle has been deployed before, <em>all</em>
processes in those older bundles are retired.</li>
+<li>ODE checks whether the same bundle has been deployed before, <em>all</em>
processes in those older bundles are retired.</li>
<li>The processes in the bundle are deployed in the engine using the same
version number as the bundle itself.</li>
<li>New executions of all newly deployed processes are ready to be
started.</li>
</ol>
@@ -112,18 +112,18 @@
<li>Banana-5(Kiwi-5)</li>
</ol>
<p>That's both tasty and healthy! </p>
-<p>There's still a last question left unsolved: what happens if you take your
bundle and deploy it under a different name with the same content. If you know
a bit about source version control (like CVS or Subversion), that's very close
to branching, only you might be executing two branches at the same time. As Ode
can't find another bundle with the same, the processes will simply be deployed
<em>without</em> retiring anything. You will effectively have twice the same
process deployed under different versions. In that scenario you're supposed to
know what you're doing. </p>
+<p>There's still a last question left unsolved: what happens if you take your
bundle and deploy it under a different name with the same content. If you know
a bit about source version control (like CVS or Subversion), that's very close
to branching, only you might be executing two branches at the same time. As ODE
can't find another bundle with the same, the processes will simply be deployed
<em>without</em> retiring anything. You will effectively have twice the same
process deployed under different versions. In that scenario you're supposed to
know what you're doing. </p>
<p>If two identical process definitions are deployed at the same time, the
behavior of the engine is unspecified. Which one of the two process will pick
up the message? Who knows!? But this can be a very useful feature in specific
cases when you want to deploy the same process twice (by same understand same
name and same namespace) but the 2 definitions are actually different and
enable different endpoints. This allows the parallel deployment of two
different version of the same process provided that they don't overlap in their
endpoint implementation.</p>
<p><a name="ProcessVersioning-RemoteDeploymentvs.Hand-MadeDeployment"></a></p>
<h4 id="remote-deployment-vs-hand-made-deployment">Remote Deployment vs.
Hand-Made Deployment</h4>
-<p>Ode supports 2 different ways of deploying bundles:</p>
+<p>ODE supports 2 different ways of deploying bundles:</p>
<ul>
<li>using the deployment web service or JBI deployment.</li>
<li>dropping bundles as directories under WEB-INF/processes.</li>
</ul>
<p>The first way works just as described previously. Under the hood, your
process bundle is a zip and it gets unzipped in a directory named
bundlename-version. The version number is automatically generated by the
engine. So you only need to provide the zip itself and a consistent bundle
name.</p>
-<p>For the second way, it's a bit more tricky. Because you're directly
interacting with the deployment directory, you're allowed to create a bundle
directory with any name you like (even not numbered at all). In that case Ode
will still create a version number, it just won't be shown on the filesystem.
However as it won't be able to find the previous bundle to retire, it will just
deploy the new bundle along with all other processes, even if you already had
some conflicting deployments. Basically, if you don't number your directories
properly, every new deployment will be a new branch. In short, you don't really
want to do that.</p>
-<p>Another thing you're allowed to do with the file system is simply to
replace (or remove and copy) all the files in the deployment bundle directory
and remove the .deployed marker file to trigger redeployment. In that case Ode
will simply consider you've undeployed and deployed the whole thing. So we get
back to the situation where we don't have any versioning. Which can be very
useful when you're in development mode because you usually don't care much
about the running instances and you usually don't want to pile up versions of
process definitions.</p>
+<p>For the second way, it's a bit more tricky. Because you're directly
interacting with the deployment directory, you're allowed to create a bundle
directory with any name you like (even not numbered at all). In that case ODE
will still create a version number, it just won't be shown on the filesystem.
However as it won't be able to find the previous bundle to retire, it will just
deploy the new bundle along with all other processes, even if you already had
some conflicting deployments. Basically, if you don't number your directories
properly, every new deployment will be a new branch. In short, you don't really
want to do that.</p>
+<p>Another thing you're allowed to do with the file system is simply to
replace (or remove and copy) all the files in the deployment bundle directory
and remove the .deployed marker file to trigger redeployment. In that case ODE
will simply consider you've undeployed and deployed the whole thing. So we get
back to the situation where we don't have any versioning. Which can be very
useful when you're in development mode because you usually don't care much
about the running instances and you usually don't want to pile up versions of
process definitions.</p>
</div>
</div>
Modified: websites/staging/ode/trunk/content/restful-bpel-part-i.html
==============================================================================
--- websites/staging/ode/trunk/content/restful-bpel-part-i.html (original)
+++ websites/staging/ode/trunk/content/restful-bpel-part-i.html Wed Dec 5
20:02:20 2012
@@ -82,7 +82,7 @@
<div class="row">
<div class="span12">
<div class="alert alert-warning">
- This feature is not yet implemented in Ode. This is a proposal and is
subject to change based on feedback, implementation experience, etc.
+ This feature is not yet implemented in ODE. This is a proposal and is
subject to change based on feedback, implementation experience, etc.
</div>
<p><a name="RESTfulBPEL,PartI-Invoke"></a></p>
Modified: websites/staging/ode/trunk/content/restful-bpel-part-ii.html
==============================================================================
--- websites/staging/ode/trunk/content/restful-bpel-part-ii.html (original)
+++ websites/staging/ode/trunk/content/restful-bpel-part-ii.html Wed Dec 5
20:02:20 2012
@@ -82,7 +82,7 @@
<div class="row">
<div class="span12">
<div class="alert alert-warning">
- This feature is not yet implemented in Ode. This is a proposal subject to
feedback, implementation experience, etc.
+ This feature is not yet implemented in ODE. This is a proposal subject to
feedback, implementation experience, etc.
</div>
<p><a name="RESTfulBPEL,PartII-UseCases"></a></p>
Modified: websites/staging/ode/trunk/content/roadmap.html
==============================================================================
--- websites/staging/ode/trunk/content/roadmap.html (original)
+++ websites/staging/ode/trunk/content/roadmap.html Wed Dec 5 20:02:20 2012
@@ -89,9 +89,9 @@
<li>BPEL 2.0 Compliance
<strong> Support <toParts> and <fromParts>
</strong> Invoking with variables that are not messages
- ** Isolated Scopes (done as of September 2007; will be Ode 1.2/2.0)</li>
+ ** Isolated Scopes (done as of September 2007; will be ODE 1.2/2.0)</li>
<li>Implement all management queries with OpenJPA</li>
-<li>Replace Quartz scheduler with something better performance-wise (done as
of June 2007; released in Ode 1.1)</li>
+<li>Replace Quartz scheduler with something better performance-wise (done as
of June 2007; released in ODE 1.1)</li>
<li>Expose management APIs in a RESTful manner (I think Axis2 supports
this?)</li>
<li>Implement a Service Component Architecture (SCA) integration layer (in
progress; basic integration released with Tuscany 1.0)</li>
<li>Add more BPEL 2.0 test cases (this is work in progress; we add test cases
as bugs are reported by the community)</li>
Modified: websites/staging/ode/trunk/content/sitemap.html
==============================================================================
--- websites/staging/ode/trunk/content/sitemap.html (original)
+++ websites/staging/ode/trunk/content/sitemap.html Wed Dec 5 20:02:20 2012
@@ -143,7 +143,7 @@
<li><a href="/pick.html">pick</a></li>
<li><a href="/port.html">port</a></li>
<li><a href="/process-contexts.html">Process Contexts</a></li>
-<li><a href="/process-versioning.html">Process Versioning * <a
href="#ProcessVersioning-Introduction">Introduction</a> * <a
href="#ProcessVersioning-HowVersioningWorks">How Versioning Works</a> * <a
href="#ProcessVersioning-ProcessVersioninginOde">Process Versioning in Ode</a>
* <a href="#ProcessVersioning-RemoteDeploymentvs.Hand-MadeDeployment">Remote
Deployment vs. Hand-Made Deployment</a></a></li>
+<li><a href="/process-versioning.html">Process Versioning * <a
href="#ProcessVersioning-Introduction">Introduction</a> * <a
href="#ProcessVersioning-HowVersioningWorks">How Versioning Works</a> * <a
href="#ProcessVersioning-ProcessVersioninginOde">Process Versioning in ODE</a>
* <a href="#ProcessVersioning-RemoteDeploymentvs.Hand-MadeDeployment">Remote
Deployment vs. Hand-Made Deployment</a></a></li>
<li><a href="/pxe-activate-command.html">pxe-activate Command</a></li>
<li><a href="/pxe-deactivate-command.html">pxe-deactivate Command</a></li>
<li><a href="/pxe-deploy-command.html">pxe-deploy Command</a></li>
Modified: websites/staging/ode/trunk/content/source-code.html
==============================================================================
--- websites/staging/ode/trunk/content/source-code.html (original)
+++ websites/staging/ode/trunk/content/source-code.html Wed Dec 5 20:02:20 2012
@@ -215,30 +215,30 @@ as duplicate section names can cause pro
<p>To verify the auto-props processing is working you can test adding a file
without committing it (Windows example):</p>
-<div class="codehilite"><pre>C:\projects\Ode>echo
testdata>test-auto-props.xml
+<div class="codehilite"><pre>C:\projects\ODE>echo
testdata>test-auto-props.xml
-C:\projects\Ode>svn add test-auto-props.xml
+C:\projects\ODE>svn add test-auto-props.xml
A test-auto-props.xml
-C:\projects\Ode>svn proplist test-auto-props.xml
+C:\projects\ODE>svn proplist test-auto-props.xml
Properties on 'test-auto-props.xml':
svn:mime-type
svn:keywords
svn:eol-style
-C:\projects\Ode>svn propget svn:mime-type test-auto-props.xml
+C:\projects\ODE>svn propget svn:mime-type test-auto-props.xml
text/xml
-C:\projects\Ode>svn propget svn:keywords test-auto-props.xml
+C:\projects\ODE>svn propget svn:keywords test-auto-props.xml
Date Author Id Revision HeadURL
-C:\projects\Ode>svn propget svn:eol-style test-auto-props.xml
+C:\projects\ODE>svn propget svn:eol-style test-auto-props.xml
native
-C:\projects\Ode>svn revert test-auto-props.xml
+C:\projects\ODE>svn revert test-auto-props.xml
Reverted 'test-auto-props.xml'
-C:\projects\Ode>del test-auto-props.xml
+C:\projects\ODE>del test-auto-props.xml
</pre></div>
Modified: websites/staging/ode/trunk/content/user-guide.html
==============================================================================
--- websites/staging/ode/trunk/content/user-guide.html (original)
+++ websites/staging/ode/trunk/content/user-guide.html Wed Dec 5 20:02:20 2012
@@ -85,7 +85,7 @@
<h2 id="getting-started">Getting Started</h2>
<p>First of all, getting familiar with the <a href="ws-bpel-2.0.html">WS-BPEL
2.0</a> standard is a very good idea. To use ODE, you will need to write
processes using the BPEL language. There are several examples in our <a
href="getting-ode.html">distributions</a> that you can use to get started, but
a decent understanding of the spec is assumed.</p>
<p>Then, you can optionally check out <a href="ode-schema.html">ODE Schema</a>
page in order to install schema for your database. Please note that schemas
from distribution sometimes contain errors, because of poor quality of ORM
schema generators.</p>
-<p>Ode can be deployed in three different environments:</p>
+<p>ODE can be deployed in three different environments:</p>
<ul>
<li>As a simple Web Service in Axis 2, ODE is bundled in a WAR than can be
deployed in any application server and is invoked using plain SOAP/HTTP.</li>
<li>As a JBI service assembly, ODE is bundled in a ZIP that can be deployed in
any JBI container and is invoked using the NMR.</li>
@@ -100,7 +100,7 @@
<li><a href="upgrading-ode.html">Upgrading ODE</a></li>
</ol>
<p><a name="UserGuide-UsingOde"></a></p>
-<h2 id="using-ode">Using Ode</h2>
+<h2 id="using-ode">Using ODE</h2>
<ol>
<li><a href="creating-a-process.html">Creating a Process</a></li>
<li><a href="process-versioning.html">Process Versioning</a></li>
Modified:
websites/staging/ode/trunk/content/using-a-jndi-datasource-under-servicemix-jbi.html
==============================================================================
---
websites/staging/ode/trunk/content/using-a-jndi-datasource-under-servicemix-jbi.html
(original)
+++
websites/staging/ode/trunk/content/using-a-jndi-datasource-under-servicemix-jbi.html
Wed Dec 5 20:02:20 2012
@@ -81,7 +81,7 @@
<div class="row">
<div class="span12">
- <p>These instructions will help you configure a JNDI DataSource for
Apache Ode when running inside the ServiceMix JBI container.</p>
+ <p>These instructions will help you configure a JNDI DataSource for
Apache ODE when running inside the ServiceMix JBI container.</p>
<p><a
name="UsingaJNDIdatasourceunderServiceMixJBI-1.Edit$SERVICEMIX/conf/jndi.xml"></a></p>
<h3 id="1-edit-servicemixconfjndixml">1. Edit $SERVICEMIX/conf/jndi.xml</h3>
<p>Declare a managed connection factory pointing to your database:</p>
@@ -97,7 +97,7 @@
<p>And register the DataSource in the JNDI registry by adding an <entry> under
the <util:map> element:</p>
<div class="codehilite"><pre> <span class="nt"><util:map</span> <span
class="na">id=</span><span class="s">"jndiEntries"</span><span
class="nt">></span>
- <span class="c"><!-- Ode DataSource --></span>
+ <span class="c"><!-- ODE DataSource --></span>
<span class="nt"><entry</span> <span class="na">key=</span><span
class="s">"java:comp/env/jdbc/ode"</span><span class="nt">></span>
<span class="nt"><bean</span> <span class="na">id=</span><span
class="s">"odeDataSource"</span> <span class="na">class=</span><span
class="s">"org.jencks.factory.ConnectionFactoryFactoryBean"</span><span
class="nt">></span>
<span class="nt"><property</span> <span
class="na">name=</span><span
class="s">"managedConnectionFactory"</span> <span
class="na">ref=</span><span
class="s">"odeManagedConnectionFactory"</span><span
class="nt">/></span>
@@ -125,7 +125,7 @@
<p>Copy <a
href="http://repository.codehaus.org/org/jencks/jencks/2.0/jencks-2.0-all.jar";>jencks-2.0-all.jar</a>
under $SERVICEMIX/lib</p>
<p><a
name="UsingaJNDIdatasourceunderServiceMixJBI-4.RestartServiceMix"></a></p>
<h3 id="4-restart-servicemix">4. Restart ServiceMix</h3>
-<p>And you're done! Don't forget to redeploy your service assemblies since
they need to be re-synchronized with Ode.</p>
+<p>And you're done! Don't forget to redeploy your service assemblies since
they need to be re-synchronized with ODE.</p>
<p><a name="UsingaJNDIdatasourceunderServiceMixJBI-Extras"></a></p>
<h3 id="extras">Extras</h3>
<p><a
name="UsingaJNDIdatasourceunderServiceMixJBI-ConnectionPoolParameters"></a></p>
Modified: websites/staging/ode/trunk/content/war-deployment.html
==============================================================================
--- websites/staging/ode/trunk/content/war-deployment.html (original)
+++ websites/staging/ode/trunk/content/war-deployment.html Wed Dec 5 20:02:20
2012
@@ -84,7 +84,7 @@
<p><a name="WARDeployment-DeployingtheWAR"></a></p>
<h4 id="deploying-the-war">Deploying the WAR</h4>
<p>Unzip the <a href="getting-ode.html">distribution</a> somewhere on your
disk, everything needed is inside.</p>
-<p>Get the WAR file in the distribution root directory, rename it to
<em>ode.war</em> and copy this file to <a
href="http://tomcat.apache.org";>Tomcat</a>'s webapp directory. Start Tomcat and
Ode should be up and running. You should get the
[Axis2|http://ws.apache.org/axis2] welcome page under
[http://localhost:8080/ode]. The Ode WAR includes its own embedded database
([Derby|http://db.apache.org/derby]) so you don't have to worry about
configuring any external database for now.</p>
+<p>Get the WAR file in the distribution root directory, rename it to
<em>ode.war</em> and copy this file to <a
href="http://tomcat.apache.org";>Tomcat</a>'s webapp directory. Start Tomcat and
ODE should be up and running. You should get the
[Axis2|http://ws.apache.org/axis2] welcome page under
[http://localhost:8080/ode]. The ODE WAR includes its own embedded database
([Derby|http://db.apache.org/derby]) so you don't have to worry about
configuring any external database for now.</p>
<p><a name="WARDeployment-Examples"></a></p>
<h4 id="examples">Examples</h4>
<p>Copy the content of the <em>examples</em> directory in the distribution
(the 3 sub-directories) to <em>tomcat/webapps/ode/WEB-INF/processes</em>, this
will automatically deploy the 3 example processes. Use the sendsoap command
located in the distribution <em>bin</em> directory to send test messages. The
messages to run each of the 3 examples are provided in their respective
directory (testRequest.soap). For each example type something like:</p>
Modified:
websites/staging/ode/trunk/content/ws-bpel-20-specification-compliance.html
==============================================================================
--- websites/staging/ode/trunk/content/ws-bpel-20-specification-compliance.html
(original)
+++ websites/staging/ode/trunk/content/ws-bpel-20-specification-compliance.html
Wed Dec 5 20:02:20 2012
@@ -92,7 +92,7 @@
<p>The inline <code>from-spec</code> used for variable initialization (BPEL
2.0 Section 8.1) is not supported, however a patch is available (see
ODE-236).</p>
<p><a name="WS-BPEL2.0SpecificationCompliance-ExternalVariables"></a></p>
<h3 id="external-variables">External Variables</h3>
-<p>In addition to regular variables that are managed by the engine according
to the BPEL specification, Ode adds support for variables whose content is
stored externally yet transparently accessible from the engine. See <a
href="external-variables.html">External Variables</a> for more information.</p>
+<p>In addition to regular variables that are managed by the engine according
to the BPEL specification, ODE adds support for variables whose content is
stored externally yet transparently accessible from the engine. See <a
href="external-variables.html">External Variables</a> for more information.</p>
<p><a name="WS-BPEL2.0SpecificationCompliance-Activities"></a></p>
<h2 id="activities">Activities</h2>
<p>In this section the divergences from the specification for each standard
BPEL activity are described. </p>
@@ -123,7 +123,7 @@
<p>The WS-BPEL 2.0 specification requires the
<code><[assign](assign.html)></code> activity to be atomic. Currently in
ODE, each <code><copy></code> is atomic. </p>
<p>The specification also provides for validating variables at the end of an
assignment using the <code>validate</code> attribute. ODE does not support
this. This means that the
<code>bpel:[invalidVariables](invalidvariables.html)</code> fault is never
thrown by an <code><[assign]></code> activity.</p>
<p>Inline assignment as part of the variable declaration isn't currently
supported.</p>
-<p>Ode currently uses the <code>expressionLanguage</code> attribute to
determine the language used in assignments instead of using the
<code>queryLanguage</code> attribute.</p>
+<p>ODE currently uses the <code>expressionLanguage</code> attribute to
determine the language used in assignments instead of using the
<code>queryLanguage</code> attribute.</p>
<p>There are no other known divergences from the specification relating to the
<code><assign></code> activity that would prevent the execution of valid
BPEL assignments. ODE provides certain (non-standard) extensions to the
<code><assign></code> activity that do not conform to the specification's
requirements for assignment extensions. Consult the <a
href="assign.html">reference page</a> for the <code><assign></code>
activity for further details regarding non-standard extensions.</p>
<p><a
name="WS-BPEL2.0SpecificationCompliance-<code><[throw](throw.html)></code>"></a></p>
<h3 id="throwthrowhtml"><code><[throw](throw.html)></code></h3>
@@ -151,7 +151,7 @@
<p>The <code><repeatUntil></code> activity is fully compliant with the
specification.</p>
<p><a
name="WS-BPEL2.0SpecificationCompliance-<code><[forEach](foreach.html)></code>"></a></p>
<h3 id="foreachforeachhtml"><code><[forEach](foreach.html)></code></h3>
-<p>The <code><forEach></code> activity is fully compliant with the
specification. Ode supports both sequential and parallel for-each
semantics.</p>
+<p>The <code><forEach></code> activity is fully compliant with the
specification. ODE supports both sequential and parallel for-each
semantics.</p>
<p><a
name="WS-BPEL2.0SpecificationCompliance-<code><[pick](pick.html)></code>"></a></p>
<h3 id="pickpickhtml"><code><[pick](pick.html)></code></h3>
<p>The <code><[pick](pick.html)></code> activity has the same issues as
the <code><[receive]></code> activity.</p>
@@ -160,7 +160,7 @@
<p>The <code><flow></code> activity is fully compliant with the
specification.</p>
<p><a
name="WS-BPEL2.0SpecificationCompliance-<code><[scope](scope.html)></code>"></a></p>
<h3 id="scopescopehtml"><code><[scope](scope.html)></code></h3>
-<p>Isolated scopes are implemented in Ode trunk (as of September 2007) and
will be released in Ode 1.2/2.0.<br />
+<p>Isolated scopes are implemented in ODE trunk (as of September 2007) and
will be released in ODE 1.2/2.0.<br />
</p>
<p>ODE v1.0/1.1 do not support isolated scopes nor do they support "exit on
standard fault" semantics. Hence, a BPEL 2.0 process will be interpreted as if
any <code>isolated</code> and <code>exitOnStandardFault</code> attributes on
<code><scope></code> elements did not exist.</p>
<p><a
name="WS-BPEL2.0SpecificationCompliance-<code><[compensate](compensate.html)></code>"></a></p>
Modified: websites/staging/ode/trunk/content/xquery-extensions.html
==============================================================================
--- websites/staging/ode/trunk/content/xquery-extensions.html (original)
+++ websites/staging/ode/trunk/content/xquery-extensions.html Wed Dec 5
20:02:20 2012
@@ -82,7 +82,7 @@
<div class="row">
<div class="span12">
<div class="alert alert-warning">
- XQuery is available only in Ode 1.3 or later
+ XQuery is available only in ODE 1.3 or later
</div>
<p>Apache ODE goes above and beyond the <a href="-ws-bpel-20.html">WS-BPEL</a>
specification by allowing the use of [XQuery 1.0|http://www.w3.org/TR/xquery/]
in queries and expressions.</p>
![http://ode.apache.org/img/ode-logo.png"](http://ode.apache.org/img/ode-logo.png"){kind=link}