You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@ode.apache.org by bu...@apache.org on 2012/12/28 14:57:56 UTC
svn commit: r844120 - in /websites/staging/ode/trunk/content: ./
developerguide/ extensions/ userguide/
Author: buildbot
Date: Fri Dec 28 13:57:55 2012
New Revision: 844120
Log:
Staging update by buildbot for ode
Added:
websites/staging/ode/trunk/content/developerguide/building-ode.html
Removed:
websites/staging/ode/trunk/content/building-ode.html
Modified:
websites/staging/ode/trunk/content/ (props changed)
websites/staging/ode/trunk/content/assign.html
websites/staging/ode/trunk/content/bpel-management-api-specification.html
websites/staging/ode/trunk/content/bpelc-command.html
websites/staging/ode/trunk/content/endpoint-configuration.html
websites/staging/ode/trunk/content/extensions/implicit-correlations.html
websites/staging/ode/trunk/content/extensions/iterable-foreach.html
websites/staging/ode/trunk/content/extensions/xpath-extensions.html
websites/staging/ode/trunk/content/extensions/xquery-extensions.html
websites/staging/ode/trunk/content/getting-ode.html
websites/staging/ode/trunk/content/index.html
websites/staging/ode/trunk/content/sitemap.html
websites/staging/ode/trunk/content/userguide/index.html
websites/staging/ode/trunk/content/ws-bpel-20-specification-compliance.html
websites/staging/ode/trunk/content/ws-bpel-20.html
Propchange: websites/staging/ode/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Dec 28 13:57:55 2012
@@ -1 +1 @@
-1426510
+1426512
Modified: websites/staging/ode/trunk/content/assign.html
==============================================================================
--- websites/staging/ode/trunk/content/assign.html (original)
+++ websites/staging/ode/trunk/content/assign.html Fri Dec 28 13:57:55 2012
@@ -234,7 +234,7 @@
<p>An attempt during process execution to read a partner link before its partnerRole EPR is initialized results in the <code>[bpel:uninitializedPartnerRole](#uninitializedpartnerrole.html)</code> standard fault. Partner roles of partner links are read when they are referenced in an <code><[invoke]></code> or the <code><from></code> part of a <code><copy></code> in an <code><[assign]></code> activity.</p>
<p><a name="assign-PropertyVariant"></a></p>
<h4 id="property-variant">Property Variant</h4>
-<p>Allows data manipulation using <a href="properties.html">properties</a>. The property value generated by the from-spec is generated in the same manner as the value returned by the <code>bpel:[getVariableProperty]()</code> function. </p>
+<p>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 <code>bpel:[getVariableProperty]()</code> function. </p>
<div class="codehilite"><pre><span class="o"><</span><span class="n">to</span><span class="o">|</span><span class="n">from</span> <span class="n">variable</span><span class="o">=</span><span class="s">"BPELVariableName"</span> <span class="n">property</span><span class="o">=</span><span class="s">"QName"</span> <span class="o">/></span>
</pre></div>
Modified: websites/staging/ode/trunk/content/bpel-management-api-specification.html
==============================================================================
--- websites/staging/ode/trunk/content/bpel-management-api-specification.html (original)
+++ websites/staging/ode/trunk/content/bpel-management-api-specification.html Fri Dec 28 13:57:55 2012
@@ -89,7 +89,7 @@
<p><a name="BPELManagementAPISpecification-GeneralDesignPrinciples"></a></p>
<h2 id="general-design-principles">General Design Principles</h2>
<p>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.</p>
-<p>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 <a href="hashmap.html">HashMap</a>. 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.</p>
+<p>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.</p>
<p>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<code>123 and customer_id</code>456" is easier to process in textual form.</p>
<p><a name="BPELManagementAPISpecification-TheProcessDefinitionManagementInterface"></a></p>
<h2 id="the-process-definition-management-interface">The Process Definition Management Interface</h2>
Modified: websites/staging/ode/trunk/content/bpelc-command.html
==============================================================================
--- websites/staging/ode/trunk/content/bpelc-command.html (original)
+++ websites/staging/ode/trunk/content/bpelc-command.html Fri Dec 28 13:57:55 2012
@@ -83,7 +83,7 @@
<div class="row">
<div class="span12">
- <p>The <code>bpelc</code> commandline tool {excerpt}compiles <a href="bpel4ws-1.1.html">BPEL4WS 1.1</a> or [WS-BPEL 2.0] processes for execution by the ODE runtime engine.{excerpt}</p>
+ <p>The <code>bpelc</code> commandline tool {excerpt}compiles <a href="bpel4ws-11.html">BPEL4WS 1.1</a> or [WS-BPEL 2.0] processes for execution by the ODE runtime engine.{excerpt}</p>
<p><a name="bpelcCommand-Synopsis"></a></p>
<h2 id="synopsis">Synopsis</h2>
<div class="codehilite"><pre><span class="n">bpelc</span> <span class="p">[</span><span class="o">-</span><span class="sx">q](-v|-vv.html) [-o directory]</span> <span class="p">[</span><span class="o">-</span><span class="n">rr</span> <span class="n">rrfile</span><span class="p">]</span> <span class="p">[</span><span class="o">-</span><span class="n">wsdl</span> <span class="n">uri</span><span class="p">]</span> <span class="n">url</span> <span class="o">...</span> <span class="n">url</span>
Added: websites/staging/ode/trunk/content/developerguide/building-ode.html
==============================================================================
--- websites/staging/ode/trunk/content/developerguide/building-ode.html (added)
+++ websites/staging/ode/trunk/content/developerguide/building-ode.html Fri Dec 28 13:57:55 2012
@@ -0,0 +1,180 @@
+<!DOCTYPE html>
+<html>
+ <head>
+ <title>Building ODE</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" />
+
+ <link href="/css/application.min.css" rel="stylesheet" media="screen">
+
+
+
+
+ </head>
+ <body>
+
+ <!-- Navbar -->
+ <div class="navbar navbar-fixed-top">
+ <div class="navbar-inner">
+ <div class="container">
+ <button type="button" class="btn btn-navbar" data-toggle="collapse" data-target=".nav-collapse">
+ <span class="icon-bar"></span>
+ <span class="icon-bar"></span>
+ <span class="icon-bar"></span>
+ </button>
+ <a class="brand" href="/index.html">Apache ODE</a>
+ <div class="nav-collapse collapse">
+ <ul class="nav">
+ <li class="">
+ <a href="/getting-ode.html">Getting ODE</a>
+ </li>
+ <li class=" dropdown">
+ <a href="/user-guide.html" class="dropdown-toggle" data-toggle="dropdown" data-target="#">Documentation<b class="caret"></b></a>
+ <ul class="dropdown-menu">
+ <li><a href="/userguide/">User Guide</a></li>
+ <li><a href="/developerguide/">Developer Guide</a></li>
+ <li><a href="/ws-bpel-20-specification-compliance.html">WS-BPEL Compliance</a></li>
+ <li><a href="/extensions/">WS-BPEL Extensions</a></li>
+ <li><a href="/faq.html">FAQ</a></li>
+ <li><a href="/roadmap.html">Roadmap</a></li>
+ <li><a href="/resource-services.html">Resources & Services</a></li>
+ <li><a href="/javadoc/">Javadoc</a></li>
+ </ul>
+ </li>
+ <li class="active dropdown">
+ <a href="#" class="dropdown-toggle" data-toggle="dropdown">Contributing<b class="caret"></b></a>
+ <ul class="dropdown-menu">
+ <li><a href="/mailing-lists.html">Mailing Lists</a></li>
+ <li><a href="/building-ode.html">Building ODE</a></li>
+ <li><a href="/source-code.html">Source Code</a></li>
+ <li><a href="http://issues.apache.org/jira/browse/ODE">Bug Tracking</a></li>
+ <li><a href="/contributors.html">Contributors</a></li>
+ <li><a href="http://www.apache.org/licenses/LICENSE-2.0">License</a></li>
+ </ul>
+ </li>
+ <li class="dropdown">
+ <a href="http://www.apache.org" class="dropdown-toggle" data-toggle="dropdown" data-target="#">The ASF<b class="caret"></b></a>
+ <ul class="dropdown-menu">
+ <li><a href="http://www.apache.org">Apache Software Foundation</a></li>
+ <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+ <li><a href="http://www.apache.org/foundation/sponsorship.html">Become a Sponsor</a></li>
+ <li><a href="http://www.apache.org/security/">Security</a></li>
+ </ul>
+ </li>
+ </ul>
+ </div>
+ </div>
+ </div>
+ </div>
+
+ <!-- Subhead -->
+
+ <header class="jumbotron subhead" id="overview">
+ <div class="container">
+
+ <h1>Building ODE</h1>
+
+ </div>
+ </header>
+
+
+ <!-- Content -->
+ <div class="container">
+
+ <div class="row">
+ <div class="span12">
+ <h1 id="overview">Overview</h1>
+<p>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 <a href="getting-ode.html">latest official distribution</a> is probably a better option.</p>
+<p><a name="BuildingODE-Gettingthesourcecode"></a></p>
+<h2 id="getting-the-source-code">Getting the source code</h2>
+<p><a name="BuildingODE-withSubversion"></a></p>
+<h3 id="with-subversion">with Subversion</h3>
+<p>First you will have to make sure that you have <a href="http://svn.tigris.org">Subversion</a>. If you don't know what Subversion is or don't have it installed, check <a href="http://svnbook.red-bean.com">here</a>. Once installed run:</p>
+<p>Development branch:</p>
+<div class="codehilite"><pre>$> svn checkout http://svn.apache.org/repos/asf/ode/trunk ode-trunk
+</pre></div>
+
+
+<p>For more information or if you have any problem with Subversion (like being behind a proxy or a firewall) check the <a href="source-code.html">Source Code</a> section.</p>
+<p><a name="BuildingODE-withGit"></a></p>
+<h3 id="with-git">with Git</h3>
+<p>The Subversion repository is mirrored by a Git repository at <a href="http://git.apache.org/ode.git">http://git.apache.org/ode.git</a> or <a href="http://github.com/apache/ode">Github</a>.
+So if you're more comfortable with Git, you can clone this repo.</p>
+<div class="codehilite"><pre>$> git clone http://git.apache.org/ode.git
+$> cd ode
+$> git checkout -b 1.X --track origin/trunk
+</pre></div>
+
+
+<p><a name="BuildingODE-BuildingWithBuildr"></a></p>
+<h2 id="building-with-buildr">Building With Buildr</h2>
+<p>ODE uses <a href="http://buildr.apache.org">Apache Buildr</a>. Buildr has a very detailed <a href="http://buildr.apache.org/installing.html">installation guide</a>, 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).</p>
+<p>Building is then pretty simple. </p>
+<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>
+
+<p>Open a command in the source root directory and run:</p>
+<div class="codehilite"><pre>$> buildr package test=no
+</pre></div>
+
+
+<p>To try the test cases bundled with ODE:</p>
+<div class="codehilite"><pre>$> buildr test
+</pre></div>
+
+
+<p>You are very welcome to contribute by running test cases and posting spotted errors into <a href="http://ode.apache.org/mailing-lists.html">mailing list</a>. </p>
+<p>To generate Eclipse project files:</p>
+<div class="codehilite"><pre>$> buildr eclipse
+</pre></div>
+
+
+<div class="alert alert-info">
+ You may use "buildr _1.4.4_ test" - like syntax to use specific buildr version.
+</div>
+
+<p>It just works! For more information about Buildr see http://buildr.apache.org/.</p>
+<p><a name="BuildingODE-Troubleshooting"></a></p>
+<h2 id="troubleshooting">Troubleshooting</h2>
+<ul>
+<li>If you get a Zlib:BufError, that's because of your version of Rubygems, just upgrade RubyGems by typing:
+ <code>gem update --system</code></li>
+</ul>
+ </div>
+ </div>
+
+
+ <!-- Footer -->
+ <footer class="footer">
+ <div class='row'>
+ <div class='span3'>
+ <img src="/img/asf.png" alt="Apache Software Foundation"/>
+ </div>
+ <div class='span9'>
+ <p><strong>Apache ODE</strong><sup>™</sup> is a top-level project at the <a href="http://www.apache.org">Apache Software Foundation<sup>™</sup></a>,
+ having graduated from the ASF Incubator in July 2007. Through a collaborative and meritocratic development process, Apache
+ projects deliver enterprise-grade, freely available software products that
+ attract large communities of users.</p>
+ <p>Apache ODE, ODE, Apache, the Apache feather logo, and the Apache ODE project logo are trademarks of The Apache Software Foundation. All other marks mentioned may be trademarks or registered trademarks of their respective owners.</p>
+ </div>
+ </div>
+ </footer>
+ </div> <!-- /container -->
+ <script src="http://code.jquery.com/jquery-latest.js"></script>
+ <script src="/js/bootstrap.min.js"></script>
+ <script type="text/javascript">
+ var _gaq = _gaq || [];
+ _gaq.push(['_setAccount', 'UA-36293077-1']);
+ _gaq.push(['_trackPageview']);
+
+ (function() {
+ var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
+ ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
+ var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
+ })();
+
+ </script>
+ </body>
+</html>
\ No newline at end of file
Modified: websites/staging/ode/trunk/content/endpoint-configuration.html
==============================================================================
--- websites/staging/ode/trunk/content/endpoint-configuration.html (original)
+++ websites/staging/ode/trunk/content/endpoint-configuration.html Fri Dec 28 13:57:55 2012
@@ -236,7 +236,7 @@ If a given property is not listed below,
| http.proxy.</em> | | Cannot be set with simple properties. Custom code added. |</p>
<p><a name="EndpointConfiguration-AdditionalConfigurationforSOAPEndpoints"></a></p>
<h3 id="additional-configuration-for-soap-endpoints">Additional Configuration for SOAP Endpoints</h3>
-<p>If you deploy ODE in an application server, the <a href="architectural-overview#odeintegrationlayers.html">Axis2 Integration Layer</a> allows ODE to communicate via Web Service interactions. SOAP Web Services will be managed by Axis2. These web services may be configured dynamically.
+<p>If you deploy ODE in an application server, the <a href="/developerguide/architectural-overview#odeintegrationlayers.html">Axis2 Integration Layer</a> 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 <code>\[serviceLocalName\](servicelocalname\.html).axis2</code> file at the root of the process bundle. Currently, this file can only be added on the server, under <code>var/processes/\{$process_dir\</code>}.</p>
<p>For example, given this wsdl: </p>
<div class="codehilite"><pre><span class="cp"><?xml version="1.0" encoding="utf-8"?></span>
Modified: websites/staging/ode/trunk/content/extensions/implicit-correlations.html
==============================================================================
--- websites/staging/ode/trunk/content/extensions/implicit-correlations.html (original)
+++ websites/staging/ode/trunk/content/extensions/implicit-correlations.html Fri Dec 28 13:57:55 2012
@@ -124,7 +124,7 @@
<p>For a complete example check <a href="https://svn.apache.org/repos/asf/ode/trunk/distro/src/examples-war/MagicSession/">MagicSession</a>.</p>
<p><a name="ImplicitCorrelations-ProcesstoServiceInteractionUseCase"></a></p>
<h3 id="process-to-service-interaction-use-case">Process to Service Interaction Use Case</h3>
-<p>See the <a href="stateful-exchange-protocol.html">Stateful Exchange Protocol</a>.</p>
+<p>See the <a href="/developerguide/stateful-exchange-protocol.html">Stateful Exchange Protocol</a>.</p>
</div>
</div>
Modified: websites/staging/ode/trunk/content/extensions/iterable-foreach.html
==============================================================================
--- websites/staging/ode/trunk/content/extensions/iterable-foreach.html (original)
+++ websites/staging/ode/trunk/content/extensions/iterable-foreach.html Fri Dec 28 13:57:55 2012
@@ -105,14 +105,14 @@
</pre></div>
-<p>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. <a href="sa00074.html">SA00074</a> 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.</p>
+<p>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.</p>
<p>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).</p>
<p>If the value of the parallel attribute is no then the activity is a serial <forEach>. The enclosed <scope> activity MUST be executed M times, each instance starting only after the previous repetition is complete. If premature termination occurs such as due to a fault, or the completion condition evaluates to true, then this M requirement does not apply. During each repetition, a variable of type specified by the instanceOf attribute is implicitly declared in the <forEach> activity's child <scope>. This implicit variable has the name specified in the rangeVariableName attribute. The first iteration of the scope will see the range variable initialized to the first item in <sequenceValue>. The next iteration will cause the range variable to be initialized to the second item in <sequenceValue>. Each subsequent iteration will move the range variable to the next item in the sequence until the final iteration where the range will be set to the last item in <sequenceValue>. The r
ange variable is local to the enclosed <scope> and although its value can be changed during an iteration, that value will be lost at the end of each iteration. Therefore, the range variable value will not affect the value of the next iteration's range.</p>
<p>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.</p>
-<p><a href="sa00076.html">SA00076</a> 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.</p>
+<p>[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.</p>
<p>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).</p>
<p>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.</p>
-<p>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. <a href="sa00075.html">SA00075</a> 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.</p>
+<p>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.</p>
<p>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.</p>
<p>The <completionCondition> is evaluated each time a directly enclosed <scope> activity completes. If the <completionCondition> evaluates to true, the <forEach> activity completes:</p>
<ul>
Modified: websites/staging/ode/trunk/content/extensions/xpath-extensions.html
==============================================================================
--- websites/staging/ode/trunk/content/extensions/xpath-extensions.html (original)
+++ websites/staging/ode/trunk/content/extensions/xpath-extensions.html Fri Dec 28 13:57:55 2012
@@ -83,7 +83,7 @@
<div class="row">
<div class="span12">
- <p>Apache ODE extends the default XPath coverage provided by the <a href="-ws-bpel-20.html">WS-BPEL</a> specification mostly by adding support for <a href="http://www.w3.org/TR/xpath20/">XPath 2.0</a> and by offering a few utility extension functions to make some assignments easier.</p>
+ <p>Apache ODE extends the default XPath coverage provided by the <a href="/ws-bpel-20.html">WS-BPEL</a> specification mostly by adding support for <a href="http://www.w3.org/TR/xpath20/">XPath 2.0</a> and by offering a few utility extension functions to make some assignments easier.</p>
<p><a name="XPathExtensions-XPath2.0"></a></p>
<h3 id="xpath-20">XPath 2.0</h3>
<p>To use XPath 2.0 in your processes just use the following <em>queryLanguage</em> and <em>expressionLanguage</em> attributes:</p>
Modified: websites/staging/ode/trunk/content/extensions/xquery-extensions.html
==============================================================================
--- websites/staging/ode/trunk/content/extensions/xquery-extensions.html (original)
+++ websites/staging/ode/trunk/content/extensions/xquery-extensions.html Fri Dec 28 13:57:55 2012
@@ -87,7 +87,7 @@
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 <a href="http://www.w3.org/TR/xquery/">XQuery 1.0</a> in queries and expressions.</p>
+<p>Apache ODE goes above and beyond the <a href="/ws-bpel-20.html">WS-BPEL</a> specification by allowing the use of <a href="http://www.w3.org/TR/xquery/">XQuery 1.0</a> in queries and expressions.</p>
<p>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.</p>
<p><a name="XQueryExtensions-XQuery1.0"></a></p>
<h3 id="xquery-10">XQuery 1.0</h3>
Modified: websites/staging/ode/trunk/content/getting-ode.html
==============================================================================
--- websites/staging/ode/trunk/content/getting-ode.html (original)
+++ websites/staging/ode/trunk/content/getting-ode.html Fri Dec 28 13:57:55 2012
@@ -131,7 +131,7 @@
<p><a name="GettingOde-1.3.4"></a></p>
<h2 id="134">1.3.4</h2>
-<p>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 <a href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310270&styleName=Html&version=12314168">changelog</a> for a complete list. Migration is necessary from 1.3.2/1.3.3, please check the <a href="Upgrading ODE#from 1.3.3 to 1.3.4">upgrade</a> page.</p>
+<p>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 <a href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310270&styleName=Html&version=12314168">changelog</a> for a complete list. Migration is necessary from 1.3.2/1.3.3, please check the <a href="upgrading-ode.html#from1.3.3to 1.3.4">upgrade</a> page.</p>
<table class="table table-bordered">
<thead>
<tr>
@@ -301,7 +301,7 @@
<p><a name="GettingOde-1.2"></a></p>
<h2 id="12">1.2</h2>
-<p>Apache ODE 1.2 packs new features as well as many small fixes and improvements. The features highlight is <a href="external-variables.html">external variables</a>, support for the WSDL HTTP binding (allowing the invocation of REST style services) and advanced endpoint configurations. See the <a href="https://issues.apache.org/jira/browse/ODE?report=com.atlassian.jira.plugin.system.project:changelog-panel">changelog</a> for the complete list of modifications and the <a href="Upgrading ODE#from 1.1 to 1.2">upgrade</a> page if applicable.</p>
+<p>Apache ODE 1.2 packs new features as well as many small fixes and improvements. The features highlight is <a href="/extensions/external-variables.html">external variables</a>, support for the WSDL HTTP binding (allowing the invocation of REST style services) and advanced endpoint configurations. See the <a href="https://issues.apache.org/jira/browse/ODE?report=com.atlassian.jira.plugin.system.project:changelog-panel">changelog</a> for the complete list of modifications and the <a href="Upgrading ODE#from 1.1 to 1.2">upgrade</a> page if applicable.</p>
<table class="table table-bordered">
<thead>
<tr>
Modified: websites/staging/ode/trunk/content/index.html
==============================================================================
--- websites/staging/ode/trunk/content/index.html (original)
+++ websites/staging/ode/trunk/content/index.html Fri Dec 28 13:57:55 2012
@@ -104,7 +104,7 @@
<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: websites/staging/ode/trunk/content/sitemap.html
==============================================================================
--- websites/staging/ode/trunk/content/sitemap.html (original)
+++ websites/staging/ode/trunk/content/sitemap.html Fri Dec 28 13:57:55 2012
@@ -95,7 +95,6 @@
<li><a href="/bpel-management-api-specification.html">BPEL Management API Specification</a></li>
<li><a href="/bpel4ws-11.html">BPEL4WS 1.1</a></li>
<li><a href="/bpelc-command.html">bpelc Command</a></li>
-<li><a href="/building-ode.html">Building ODE</a></li>
<li><a href="/compensate.html">compensate</a></li>
<li><a href="/contributors.html">Contributors</a></li>
<li><a href="/copy-with-insert-attribute.html">copy with insert attribute</a></li>
Modified: websites/staging/ode/trunk/content/userguide/index.html
==============================================================================
--- websites/staging/ode/trunk/content/userguide/index.html (original)
+++ websites/staging/ode/trunk/content/userguide/index.html Fri Dec 28 13:57:55 2012
@@ -110,8 +110,8 @@
<li><a href="/instance-replayer.html">Instance Replayer</a></li>
<li><a href="/ode-execution-events.html">ODE Execution Events</a></li>
<li><a href="/endpoint-references.html">Endpoint References</a></li>
-<li><a href="/wsdl-1.1-http-binding-support.html">WSDL 1.1 HTTP Binding Support</a></li>
-<li><a href="/wsdl-1.1-extensions-for-rest.html">WSDL 1.1 Extensions for REST</a></li>
+<li><a href="/wsdl-11-http-binding-support.html">WSDL 1.1 HTTP Binding Support</a></li>
+<li><a href="/wsdl-11-extensions-for-rest.html">WSDL 1.1 Extensions for REST</a></li>
<li><a href="/extensions/">BPEL Extensions</a></li>
<li><a href="/instance-data-cleanup.html">Instance Data Cleanup</a></li>
<li><a href="/direct-process-to-process-communication.html">Direct Process-to-Process Communication</a></li>
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 Fri Dec 28 13:57:55 2012
@@ -94,7 +94,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="/extensions/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>
Modified: websites/staging/ode/trunk/content/ws-bpel-20.html
==============================================================================
--- websites/staging/ode/trunk/content/ws-bpel-20.html (original)
+++ websites/staging/ode/trunk/content/ws-bpel-20.html Fri Dec 28 13:57:55 2012
@@ -93,7 +93,7 @@
<a href="http://www.oasis-open.org/committees/download.php/23068/WS-BPEL%20Technical%20Overview%20for%20Developers%20and%20Architects%20-%20Part%201%20%28Frank%20Ryan%29.pdf">Technical overview part 1</a>
<a href="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 2</a>
<a href="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">Technical overview part 3</a></p>
-<p>ODE's support of the specification is outlined on the <a href="ws-bpel-2.0-specification-compliance.html">WS-BPEL 2.0 Specification Compliance</a> page.</p>
+<p>ODE's support of the specification is outlined on the <a href="ws-bpel-20-specification-compliance.html">WS-BPEL 2.0 Specification Compliance</a> page.</p>
<p>ODE also supports <a href="/extensions/">a few extensions</a> to WS-BPEL in the areas we thought necessary.</p>
</div>
</div>