Author: vanto
Date: Fri Dec 28 13:57:14 2012
New Revision: 1426512
URL: http://svn.apache.org/viewvc?rev=1426512&view=rev
Log:
link fixes.
Added:
ode/site/trunk/content/developerguide/building-ode.mdtext
Removed:
ode/site/trunk/content/building-ode.mdtext
Modified:
ode/site/trunk/content/assign.mdtext
ode/site/trunk/content/bpel-management-api-specification.mdtext
ode/site/trunk/content/bpelc-command.mdtext
ode/site/trunk/content/endpoint-configuration.mdtext
ode/site/trunk/content/extensions/implicit-correlations.mdtext
ode/site/trunk/content/extensions/iterable-foreach.mdtext
ode/site/trunk/content/extensions/xpath-extensions.mdtext
ode/site/trunk/content/extensions/xquery-extensions.mdtext
ode/site/trunk/content/getting-ode.mdtext
ode/site/trunk/content/index.mdtext
ode/site/trunk/content/userguide/index.mdtext
ode/site/trunk/content/ws-bpel-20-specification-compliance.mdtext
ode/site/trunk/content/ws-bpel-20.mdtext
Modified: ode/site/trunk/content/assign.mdtext
URL:
http://svn.apache.org/viewvc/ode/site/trunk/content/assign.mdtext?rev=1426512&r1=1426511&r2=1426512&view=diff
==============================================================================
--- ode/site/trunk/content/assign.mdtext (original)
+++ ode/site/trunk/content/assign.mdtext Fri Dec 28 13:57:14 2012
@@ -165,7 +165,7 @@ An attempt during process execution to r
<a name="assign-PropertyVariant"></a>
#### Property Variant
-Allows data manipulation using [properties](properties.html). The property
value generated by the from-spec is generated in the same manner as the value
returned by the `bpel:[getVariableProperty]()` function.
+Allows data manipulation using properties. The property value generated by the
from-spec is generated in the same manner as the value returned by the
`bpel:[getVariableProperty]()` function.
<to|from variable="BPELVariableName" property="QName" />
Modified: ode/site/trunk/content/bpel-management-api-specification.mdtext
URL:
http://svn.apache.org/viewvc/ode/site/trunk/content/bpel-management-api-specification.mdtext?rev=1426512&r1=1426511&r2=1426512&view=diff
==============================================================================
--- ode/site/trunk/content/bpel-management-api-specification.mdtext (original)
+++ ode/site/trunk/content/bpel-management-api-specification.mdtext Fri Dec 28
13:57:14 2012
@@ -7,7 +7,7 @@ The BPEL Management API {excerpt} expose
## General Design Principles
The Process Management API is defined as a Web service interface. In doing so
we can offer SOAP access to the service, and also create Java interfaces for
SOAP access and JMX, depending on needs. All messages are defined as XML
elements, mapping to WSDL doc/literal.
-Complex structures and other data fields are declared as XML elements.
However, key fields are declared as XML attributes. This distinction maps to
the concept of keys in several languages, e.g. constraints can be applied in
XML Schema using key fields, or used as keys in a Java [HashMap](hashmap.html).
Sequences of elements map to ordered collections, which may be accessed by
position or key. For example, when returning a list of process instances, the
collections is ordered as specified in the request, but in addition the process
identifier can be used as a key into the collection.
+Complex structures and other data fields are declared as XML elements.
However, key fields are declared as XML attributes. This distinction maps to
the concept of keys in several languages, e.g. constraints can be applied in
XML Schema using key fields, or used as keys in a Java HashMap. Sequences of
elements map to ordered collections, which may be accessed by position or key.
For example, when returning a list of process instances, the collections is
ordered as specified in the request, but in addition the process identifier can
be used as a key into the collection.
When data does not easily yield to structuring, we use a textual presentation
and BNF to define the syntax. For example, a query statement like "order_id`123
and customer_id`456" is easier to process in textual form.
Modified: ode/site/trunk/content/bpelc-command.mdtext
URL:
http://svn.apache.org/viewvc/ode/site/trunk/content/bpelc-command.mdtext?rev=1426512&r1=1426511&r2=1426512&view=diff
==============================================================================
--- ode/site/trunk/content/bpelc-command.mdtext (original)
+++ ode/site/trunk/content/bpelc-command.mdtext Fri Dec 28 13:57:14 2012
@@ -1,5 +1,5 @@
Title: bpelc Command
-The `bpelc` commandline tool {excerpt}compiles [BPEL4WS 1.1](bpel4ws-1.1.html)
or [WS-BPEL 2.0] processes for execution by the ODE runtime engine.{excerpt}
+The `bpelc` commandline tool {excerpt}compiles [BPEL4WS 1.1](bpel4ws-11.html)
or [WS-BPEL 2.0] processes for execution by the ODE runtime engine.{excerpt}
<a name="bpelcCommand-Synopsis"></a>
## Synopsis
Added: ode/site/trunk/content/developerguide/building-ode.mdtext
URL:
http://svn.apache.org/viewvc/ode/site/trunk/content/developerguide/building-ode.mdtext?rev=1426512&view=auto
==============================================================================
--- ode/site/trunk/content/developerguide/building-ode.mdtext (added)
+++ ode/site/trunk/content/developerguide/building-ode.mdtext Fri Dec 28
13:57:14 2012
@@ -0,0 +1,77 @@
+Title: Building ODE
+Category: contributing
+
+# Overview
+Building from the source is usually for the thick skinned, we try to keep our
trunk stable but it's a development environment so we can never guarantee that
everything will be smooth. If you rather work with something more stable or if
you don't need the latest and greatest, using the [latest official
distribution](getting-ode.html) is probably a better option.
+
+<a name="BuildingODE-Gettingthesourcecode"></a>
+## Getting the source code
+
+<a name="BuildingODE-withSubversion"></a>
+### with Subversion
+
+First you will have to make sure that you have
[Subversion](http://svn.tigris.org). If you don't know what Subversion is or
don't have it installed, check [here](http://svnbook.red-bean.com). Once
installed run:
+
+Development branch:
+
+ :::text
+ $> svn checkout http://svn.apache.org/repos/asf/ode/trunk ode-trunk
+
+
+For more information or if you have any problem with Subversion (like being
behind a proxy or a firewall) check the [Source Code](source-code.html) section.
+
+<a name="BuildingODE-withGit"></a>
+### with Git
+
+The Subversion repository is mirrored by a Git repository at
[http://git.apache.org/ode.git](http://git.apache.org/ode.git) or
[Github](http://github.com/apache/ode).
+So if you're more comfortable with Git, you can clone this repo.
+
+ :::text
+ $> git clone http://git.apache.org/ode.git
+ $> cd ode
+ $> git checkout -b 1.X --track origin/trunk
+
+
+<a name="BuildingODE-BuildingWithBuildr"></a>
+## Building With Buildr
+
+ODE uses [Apache Buildr](http://buildr.apache.org). Buildr has a very detailed
[installation guide](http://buildr.apache.org/installing.html), so refer to it
to get Buildr working on your machine.
+The latest known working configuration for trunk (both for windows, linux,
macos with JDK 1.5 and JDK 1.6) is buildr 1.4.4, jruby 1.5.1 (ruby 1.8.7
patchlevel 174).
+
+Building is then pretty simple.
+
+<div class="alert alert-info"><h4 class="alert-heading">Version
Information</h4>
+ The trunk must be build with Buildr <b>1.4.4</b> or higher
+</div>
+
+Open a command in the source root directory and run:
+
+ :::text
+ $> buildr package test=no
+
+
+To try the test cases bundled with ODE:
+
+ :::text
+ $> buildr test
+
+
+You are very welcome to contribute by running test cases and posting spotted
errors into [mailing list](http://ode.apache.org/mailing-lists.html).
+
+To generate Eclipse project files:
+
+ :::text
+ $> buildr eclipse
+
+
+<div class="alert alert-info">
+ You may use "buildr _1.4.4_ test" - like syntax to use specific buildr
version.
+</div>
+
+It just works! For more information about Buildr see http://buildr.apache.org/.
+
+<a name="BuildingODE-Troubleshooting"></a>
+## Troubleshooting
+
+* If you get a Zlib:BufError, that's because of your version of Rubygems, just
upgrade RubyGems by typing:
+ ```gem update --system```
\ No newline at end of file
Modified: ode/site/trunk/content/endpoint-configuration.mdtext
URL:
http://svn.apache.org/viewvc/ode/site/trunk/content/endpoint-configuration.mdtext?rev=1426512&r1=1426511&r2=1426512&view=diff
==============================================================================
--- ode/site/trunk/content/endpoint-configuration.mdtext (original)
+++ ode/site/trunk/content/endpoint-configuration.mdtext Fri Dec 28 13:57:14
2012
@@ -172,7 +172,7 @@ If a given property is not listed below,
<a name="EndpointConfiguration-AdditionalConfigurationforSOAPEndpoints"></a>
### Additional Configuration for SOAP Endpoints
-If you deploy ODE in an application server, the [Axis2 Integration
Layer](architectural-overview#odeintegrationlayers.html) allows ODE to
communicate via Web Service interactions. SOAP Web Services will be managed by
Axis2. These web services may be configured dynamically.
+If you deploy ODE in an application server, the [Axis2 Integration
Layer](/developerguide/architectural-overview#odeintegrationlayers.html) allows
ODE to communicate via Web Service interactions. SOAP Web Services will be
managed by Axis2. These web services may be configured dynamically.
For each service, you need to place a
`\[serviceLocalName\](servicelocalname\.html).axis2` file at the root of the
process bundle. Currently, this file can only be added on the server, under
`var/processes/\{$process_dir\`}.
Modified: ode/site/trunk/content/extensions/implicit-correlations.mdtext
URL:
http://svn.apache.org/viewvc/ode/site/trunk/content/extensions/implicit-correlations.mdtext?rev=1426512&r1=1426511&r2=1426512&view=diff
==============================================================================
--- ode/site/trunk/content/extensions/implicit-correlations.mdtext (original)
+++ ode/site/trunk/content/extensions/implicit-correlations.mdtext Fri Dec 28
13:57:14 2012
@@ -52,4 +52,4 @@ For a complete example check [MagicSessi
<a name="ImplicitCorrelations-ProcesstoServiceInteractionUseCase"></a>
### Process to Service Interaction Use Case
-See the [Stateful Exchange Protocol](stateful-exchange-protocol.html).
+See the [Stateful Exchange
Protocol](/developerguide/stateful-exchange-protocol.html).
Modified: ode/site/trunk/content/extensions/iterable-foreach.mdtext
URL:
http://svn.apache.org/viewvc/ode/site/trunk/content/extensions/iterable-foreach.mdtext?rev=1426512&r1=1426511&r2=1426512&view=diff
==============================================================================
--- ode/site/trunk/content/extensions/iterable-foreach.mdtext (original)
+++ ode/site/trunk/content/extensions/iterable-foreach.mdtext Fri Dec 28
13:57:14 2012
@@ -28,7 +28,7 @@ The <forEach> activity will execute its
-When the <forEach> activity is started, the expression in <sequenceValue> is
evaluated. Once that value is returned it remains constant for the lifespan of
the activity. [SA00074](sa00074.html) That expressions MUST return a sequence
of items (meaning it comprises nodes, texts or atomic values), where ach item
can be validated to be the type specified by the instanceOf attribute. If that
expression does not return a valid sequence value, a
bpel:invalidExpressionValue fault will be thrown (see section 8.3.
Expressions). If the <sequenceValue> is empty, then the child <scope> activity
MUST NOT be performed and the <forEach> activity is complete.
+When the <forEach> activity is started, the expression in <sequenceValue> is
evaluated. Once that value is returned it remains constant for the lifespan of
the activity. \[SA00074\] That expressions MUST return a sequence of items
(meaning it comprises nodes, texts or atomic values), where ach item can be
validated to be the type specified by the instanceOf attribute. If that
expression does not return a valid sequence value, a
bpel:invalidExpressionValue fault will be thrown (see section 8.3.
Expressions). If the <sequenceValue> is empty, then the child <scope> activity
MUST NOT be performed and the <forEach> activity is complete.
The child activity of a <forEach> MUST be a <scope> activity. The <forEach>
construct introduces an implicit range variable, and also introduces dynamic
parallelism (i.e. having parallel branches of which number is not known ahead
of time). The <scope> activity provides a well-defined scope snapshot semantic
and a way to name the dynamic parallel work for compensation purposes (see
scope snapshot description in section 12.4.2. Process State Usage in
Compensation Handlers).
@@ -36,13 +36,13 @@ If the value of the parallel attribute i
If the value of the parallel attribute is yes then the activity is a parallel
<forEach>. The enclosed <scope> activity MUST be concurrently executed M times.
In essence an implicit <flow> is dynamically created with M copies of the
<forEach>'s enclosed <scope> activity as children. Each copy of the <scope>
activity will have the same range variable declared in the same manner as
specified for serial <forEach>. Each instance's range variable MUST be uniquely
initialized in parallel to one of the teim values starting with first and up
to and including the last item in <sequenceValue>, as a part of <scope>
instantiation.
-[SA00076](sa00076.html) If a variable of the same name as the value of the
rangeName attribute is declared explicitly in the enclosed scope, it would be
considered a case of duplicate variable declaration and MUST be reported as an
error during static analysis.
+\[SA00076\] If a variable of the same name as the value of the rangeName
attribute is declared explicitly in the enclosed scope, it would be considered
a case of duplicate variable declaration and MUST be reported as an error
during static analysis.
The <forEach> activity without a <completionCondition> completes when all of
its child <scope>'s have completed. The <completionCondition> element is
optionally specified to prevent some of the children from executing (in the
serial case), or to force early termination of some of the children (in the
parallel case).
The <branches> element represents an unsigned-integer expression (see section
8.3.4. Unsigned Integer Expressions) used to define a completion condition of
the "at least N out of M" form. The actual value B of the expression is
calculated once, at the beginning of the <forEach> activity. It will not change
as the result of the <forEach> activity's execution. At the end of execution of
each directly enclosed <scope> activity, the number of completed children is
compared to B, the value of the <branches> expression. If at least B children
have completed, the <completionCondition> is triggered: No further children
will be started, and currently running children will be terminated (see section
12.6 Termination Handlers). Note that enforcing the semantic of "exactly N out
of M" in parallel <forEach> would involve a race condition, and is therefore
not specified.
-When the completion condition B is calculated, if its value is larger than the
number of directly enclosed activities M, then the standard
bpel:invalidBranchCondition fault MUST be thrown. [SA00075](sa00075.html) Both
B and M may be constant expressions, and in such cases, static analysis SHOULD
reject processes where it can be detected that B is greater than M.
+When the completion condition B is calculated, if its value is larger than the
number of directly enclosed activities M, then the standard
bpel:invalidBranchCondition fault MUST be thrown. \[SA00075\] Both B and M may
be constant expressions, and in such cases, static analysis SHOULD reject
processes where it can be detected that B is greater than M.
The <branches> element has an optional successfulBranchesOnly attribute with
the default value of no. If the value of successfulBranchesOnly is no, all
<scope>'s which have completed (successfully or unsuccessfully) MUST be
counted. If successfulBranchesOnly is yes, only <scope>'s which have completed
successfully MUST be counted.
Modified: ode/site/trunk/content/extensions/xpath-extensions.mdtext
URL:
http://svn.apache.org/viewvc/ode/site/trunk/content/extensions/xpath-extensions.mdtext?rev=1426512&r1=1426511&r2=1426512&view=diff
==============================================================================
--- ode/site/trunk/content/extensions/xpath-extensions.mdtext (original)
+++ ode/site/trunk/content/extensions/xpath-extensions.mdtext Fri Dec 28
13:57:14 2012
@@ -1,5 +1,5 @@
Title: XPath Extensions
-Apache ODE extends the default XPath coverage provided by the
[WS-BPEL](-ws-bpel-20.html) specification mostly by adding support for [XPath
2.0](http://www.w3.org/TR/xpath20/) and by offering a few utility extension
functions to make some assignments easier.
+Apache ODE extends the default XPath coverage provided by the
[WS-BPEL](/ws-bpel-20.html) specification mostly by adding support for [XPath
2.0](http://www.w3.org/TR/xpath20/) and by offering a few utility extension
functions to make some assignments easier.
<a name="XPathExtensions-XPath2.0"></a>
### XPath 2.0
Modified: ode/site/trunk/content/extensions/xquery-extensions.mdtext
URL:
http://svn.apache.org/viewvc/ode/site/trunk/content/extensions/xquery-extensions.mdtext?rev=1426512&r1=1426511&r2=1426512&view=diff
==============================================================================
--- ode/site/trunk/content/extensions/xquery-extensions.mdtext (original)
+++ ode/site/trunk/content/extensions/xquery-extensions.mdtext Fri Dec 28
13:57:14 2012
@@ -3,7 +3,7 @@ Title: XQuery Extensions
XQuery is available only in ODE 1.3 or later
</div>
-Apache ODE goes above and beyond the [WS-BPEL](-ws-bpel-20.html) specification
by allowing the use of [XQuery 1.0](http://www.w3.org/TR/xquery/) in queries
and expressions.
+Apache ODE goes above and beyond the [WS-BPEL](/ws-bpel-20.html) specification
by allowing the use of [XQuery 1.0](http://www.w3.org/TR/xquery/) in queries
and expressions.
Unless specified otherwise, WS-BPEL considers XPath 1.0 to be the
query/expression language, which is denoted by the default value of the
"queryLanguage" and "expressionLanguage" attributes, viz.
"urn:oasis:names:tc:wsbpel:2.0:sublang:xpath1.0". In addition, we have
out-of-the-box support for XPath 2.0.
Modified: ode/site/trunk/content/getting-ode.mdtext
URL:
http://svn.apache.org/viewvc/ode/site/trunk/content/getting-ode.mdtext?rev=1426512&r1=1426511&r2=1426512&view=diff
==============================================================================
--- ode/site/trunk/content/getting-ode.mdtext (original)
+++ ode/site/trunk/content/getting-ode.mdtext Fri Dec 28 13:57:14 2012
@@ -54,7 +54,7 @@ Apache ODE 1.3.5 includes about 30 bug f
<a name="GettingOde-1.3.4"></a>
## 1.3.4
-Apache ODE 1.3.4 includes about 100 bug fixes and improvements (among others:
instance replaying, process deployments via OSGi bundles and spring
configurable process properties. See the
[changelog](https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310270&styleName=Html&version=12314168)
for a complete list. Migration is necessary from 1.3.2/1.3.3, please check the
[upgrade](Upgrading ODE#from 1.3.3 to 1.3.4) page.
+Apache ODE 1.3.4 includes about 100 bug fixes and improvements (among others:
instance replaying, process deployments via OSGi bundles and spring
configurable process properties. See the
[changelog](https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310270&styleName=Html&version=12314168)
for a complete list. Migration is necessary from 1.3.2/1.3.3, please check the
[upgrade](upgrading-ode.html#from1.3.3to 1.3.4) page.
<table class="table table-bordered">
<thead>
@@ -233,7 +233,7 @@ Apache ODE 1.3.2 includes many features
<a name="GettingOde-1.2"></a>
## 1.2
-Apache ODE 1.2 packs new features as well as many small fixes and
improvements. The features highlight is [external
variables](external-variables.html), support for the WSDL HTTP binding
(allowing the invocation of REST style services) and advanced endpoint
configurations. See the
[changelog](https://issues.apache.org/jira/browse/ODE?report=com.atlassian.jira.plugin.system.project:changelog-panel)
for the complete list of modifications and the [upgrade](Upgrading ODE#from
1.1 to 1.2) page if applicable.
+Apache ODE 1.2 packs new features as well as many small fixes and
improvements. The features highlight is [external
variables](/extensions/external-variables.html), support for the WSDL HTTP
binding (allowing the invocation of REST style services) and advanced endpoint
configurations. See the
[changelog](https://issues.apache.org/jira/browse/ODE?report=com.atlassian.jira.plugin.system.project:changelog-panel)
for the complete list of modifications and the [upgrade](Upgrading ODE#from
1.1 to 1.2) page if applicable.
<table class="table table-bordered">
<thead>
Modified: ode/site/trunk/content/index.mdtext
URL:
http://svn.apache.org/viewvc/ode/site/trunk/content/index.mdtext?rev=1426512&r1=1426511&r2=1426512&view=diff
==============================================================================
--- ode/site/trunk/content/index.mdtext (original)
+++ ode/site/trunk/content/index.mdtext Fri Dec 28 13:57:14 2012
@@ -31,7 +31,7 @@ WS-BPEL (Business Process Execution Lang
<li><i class="icon-check"></i> Side-by-side support for both the <a
href="ws-bpel-20.html">WS-BPEL 2.0</a> OASIS standard and the legacy BPEL4WS
1.1 vendor specification.</li>
<li><i class="icon-check"></i> Supports 2 communication layers: one
based on Axis2 (Web Services http transport) and another one based on the <a
href="http://jcp.org/en/jsr/detail?id=208";>JBI standard</a> (using <a
href="http://servicemix.apache.org";>ServiceMix</a>).</li>
<li><i class="icon-check"></i> Support for the HTTP WSDL binding,
allowing invocation of REST-style web services.</li>
- <li><i class="icon-check"></i> Possibility to map process variables <a
href="external-variables.html">externally</a> to a database table of your
choice.</li>
+ <li><i class="icon-check"></i> Possibility to map process variables <a
href="/extensions/external-variables.html">externally</a> to a database table
of your choice.</li>
<li><i class="icon-check"></i> High level API to the engine that allows
you to integrate the core with virtually any communication layer.</li>
<li><i class="icon-check"></i> Hot-deployment of your processes.</li>
<li><i class="icon-check"></i> Compiled approach to BPEL that provides
detailed analysis and validation at the <a href="bpelc-command.html">command
line</a> or at deployment.</li>
Modified: ode/site/trunk/content/userguide/index.mdtext
URL:
http://svn.apache.org/viewvc/ode/site/trunk/content/userguide/index.mdtext?rev=1426512&r1=1426511&r2=1426512&view=diff
==============================================================================
--- ode/site/trunk/content/userguide/index.mdtext (original)
+++ ode/site/trunk/content/userguide/index.mdtext Fri Dec 28 13:57:14 2012
@@ -29,8 +29,8 @@ ODE can be deployed in three different e
1. [Instance Replayer](/instance-replayer.html)
1. [ODE Execution Events](/ode-execution-events.html)
1. [Endpoint References](/endpoint-references.html)
-1. [WSDL 1.1 HTTP Binding Support](/wsdl-1.1-http-binding-support.html)
-1. [WSDL 1.1 Extensions for REST](/wsdl-1.1-extensions-for-rest.html)
+1. [WSDL 1.1 HTTP Binding Support](/wsdl-11-http-binding-support.html)
+1. [WSDL 1.1 Extensions for REST](/wsdl-11-extensions-for-rest.html)
1. [BPEL Extensions](/extensions/)
1. [Instance Data Cleanup](/instance-data-cleanup.html)
1. [Direct Process-to-Process
Communication](/direct-process-to-process-communication.html)
Modified: ode/site/trunk/content/ws-bpel-20-specification-compliance.mdtext
URL:
http://svn.apache.org/viewvc/ode/site/trunk/content/ws-bpel-20-specification-compliance.mdtext?rev=1426512&r1=1426511&r2=1426512&view=diff
==============================================================================
--- ode/site/trunk/content/ws-bpel-20-specification-compliance.mdtext (original)
+++ ode/site/trunk/content/ws-bpel-20-specification-compliance.mdtext Fri Dec
28 13:57:14 2012
@@ -16,7 +16,7 @@ The inline `from-spec` used for variable
<a name="WS-BPEL2.0SpecificationCompliance-ExternalVariables"></a>
### External Variables
-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 [External
Variables](external-variables.html) for more information.
+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 [External
Variables](/extensions/external-variables.html) for more information.
<a name="WS-BPEL2.0SpecificationCompliance-Activities"></a>
## Activities
Modified: ode/site/trunk/content/ws-bpel-20.mdtext
URL:
http://svn.apache.org/viewvc/ode/site/trunk/content/ws-bpel-20.mdtext?rev=1426512&r1=1426511&r2=1426512&view=diff
==============================================================================
--- ode/site/trunk/content/ws-bpel-20.mdtext (original)
+++ ode/site/trunk/content/ws-bpel-20.mdtext Fri Dec 28 13:57:14 2012
@@ -13,6 +13,6 @@ The presentation documents are also avai
[Technical overview part
2](http://www.oasis-open.org/committees/download.php/23067/WS-BPEL%20Technical%20Overview%20for%20Developers%20and%20Architects%20-%20Part%202%20%28Dieter%20Koenig%29.pdf)
[Technical overview part
3](http://www.oasis-open.org/committees/download.php/23066/WS-BPEL%20Technical%20Overview%20for%20Developers%20and%20Architects%20-%20Part%203%20%28Charlton%20Barreto%29.pdf)
-ODE's support of the specification is outlined on the [WS-BPEL 2.0
Specification Compliance](ws-bpel-2.0-specification-compliance.html) page.
+ODE's support of the specification is outlined on the [WS-BPEL 2.0
Specification Compliance](ws-bpel-20-specification-compliance.html) page.
ODE also supports [a few extensions](/extensions/) to WS-BPEL in the areas we
thought necessary.
