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:13:48 UTC
svn commit: r844111 [4/6] - in /websites/staging/ode/trunk/content: ./
developerguide/ extensions/ userguide/
Modified: websites/staging/ode/trunk/content/required-third-party-libraries.html
==============================================================================
--- websites/staging/ode/trunk/content/required-third-party-libraries.html (original)
+++ websites/staging/ode/trunk/content/required-third-party-libraries.html Fri Dec 28 13:13:46 2012
@@ -34,7 +34,7 @@
<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="/bpel-extensions.html">WS-BPEL Extensions</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>
Modified: websites/staging/ode/trunk/content/resource-services.html
==============================================================================
--- websites/staging/ode/trunk/content/resource-services.html (original)
+++ websites/staging/ode/trunk/content/resource-services.html Fri Dec 28 13:13:46 2012
@@ -34,7 +34,7 @@
<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="/bpel-extensions.html">WS-BPEL Extensions</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>
Modified: websites/staging/ode/trunk/content/roadmap.html
==============================================================================
--- websites/staging/ode/trunk/content/roadmap.html (original)
+++ websites/staging/ode/trunk/content/roadmap.html Fri Dec 28 13:13:46 2012
@@ -34,7 +34,7 @@
<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="/bpel-extensions.html">WS-BPEL Extensions</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>
Modified: websites/staging/ode/trunk/content/sendsoap-command.html
==============================================================================
--- websites/staging/ode/trunk/content/sendsoap-command.html (original)
+++ websites/staging/ode/trunk/content/sendsoap-command.html Fri Dec 28 13:13:46 2012
@@ -34,7 +34,7 @@
<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="/bpel-extensions.html">WS-BPEL Extensions</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>
Modified: websites/staging/ode/trunk/content/service-providers.html
==============================================================================
--- websites/staging/ode/trunk/content/service-providers.html (original)
+++ websites/staging/ode/trunk/content/service-providers.html Fri Dec 28 13:13:46 2012
@@ -34,7 +34,7 @@
<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="/bpel-extensions.html">WS-BPEL Extensions</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>
Modified: websites/staging/ode/trunk/content/service.html
==============================================================================
--- websites/staging/ode/trunk/content/service.html (original)
+++ websites/staging/ode/trunk/content/service.html Fri Dec 28 13:13:46 2012
@@ -34,7 +34,7 @@
<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="/bpel-extensions.html">WS-BPEL Extensions</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>
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:13:46 2012
@@ -34,7 +34,7 @@
<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="/bpel-extensions.html">WS-BPEL Extensions</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>
@@ -86,12 +86,10 @@
<ul>
<li><a href="/abstract-wsdl.html">abstract WSDL</a></li>
<li><a href="/activities.html">Activities</a></li>
-<li><a href="/activity-failure-and-recovery.html">Activity Failure and Recovery</a></li>
<li><a href="/agha86.html">Agha86</a></li>
<li><a href="/ambiguousreceive.html">ambiguousReceive</a></li>
<li><a href="/assign.html">assign</a></li>
<li><a href="/bibliography.html">Bibliography</a></li>
-<li><a href="/bpel-extensions.html">BPEL Extensions</a></li>
<li><a href="/bpel-language-guide.html">BPEL Language Guide</a></li>
<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>
@@ -100,46 +98,30 @@
<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>
-<li><a href="/creating-a-process.html">Creating a Process</a></li>
<li><a href="/deployment-unit.html">deployment unit</a></li>
<li><a href="/deployxml.html">deploy.xml</a></li>
-<li><a href="/direct-process-to-process-communication.html">Direct Process-to-Process Communication</a></li>
<li><a href="/endpoint-configuration.html">Endpoint Configuration</a></li>
-<li><a href="/endpoint-references.html">Endpoint References</a></li>
<li><a href="/exported-port.html">exported port</a></li>
<li><a href="/expression-languages.html">Expression Languages</a></li>
-<li><a href="/external-variables.html">External Variables</a></li>
<li><a href="/faq.html">Frequently Asked Questions</a></li>
-<li><a href="/flexible-assigns.html">Flexible Assigns</a></li>
<li><a href="/getting-ode.html">Getting ODE</a></li>
<li><a href="/glossary.html">Glossary</a></li>
-<li><a href="/headers-handling.html">Headers Handling</a></li>
<li><a href="/http-authentication.html">HTTP Authentication</a></li>
<li><a href="/http-soap-protocol-adapter.html">HTTP-SOAP Protocol Adapter</a></li>
-<li><a href="/implicit-correlations.html">Implicit Correlations * <a href="#ImplicitCorrelations-Introduction">Introduction</a> * <a href="#ImplicitCorrelations-ProcesstoProcessInteractionUseCase">Process to Process Interaction Use Case</a> * <a href="#ImplicitCorrelations-ProcesstoServiceInteractionUseCase">Process to Service Interaction Use Case</a></a></li>
<li><a href="/imported-port.html">imported port</a></li>
<li><a href="/index.html">Apache ODE<sup>â¢</sup></a></li>
-<li><a href="/instance-data-cleanup.html">Instance Data Cleanup</a></li>
-<li><a href="/instance-replayer.html">Instance Replayer</a></li>
<li><a href="/integration-layer.html">Integration Layer</a></li>
<li><a href="/invalidvariables.html">invalidVariables</a></li>
<li><a href="/invoke.html">invoke</a></li>
-<li><a href="/iterable-foreach.html">Iterable ForEach</a></li>
<li><a href="/logo.html">Logo</a></li>
<li><a href="/mailing-lists.html">Mailing Lists</a></li>
-<li><a href="/management-api.html">Management API</a></li>
<li><a href="/message-exchange.html">message exchange</a></li>
-<li><a href="/ode-execution-events.html">ODE Execution Events</a></li>
<li><a href="/ode-jbi-and-axis2-properties-overview.html">ODE Jbi and Axis2 properties overview</a></li>
<li><a href="/ode-schema.html">ODE Schema</a></li>
<li><a href="/pick.html">pick</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="/receive.html">receive</a></li>
<li><a href="/required-third-party-libraries.html">Required Third-Party Libraries</a></li>
<li><a href="/resource-services.html">Resources & Services</a></li>
-<li><a href="/restful-bpel-part-i.html">RESTful BPEL, Part I</a></li>
-<li><a href="/restful-bpel-part-ii.html">RESTful BPEL, Part II</a></li>
<li><a href="/roadmap.html">Roadmap</a></li>
<li><a href="/sendsoap-command.html">sendsoap Command</a></li>
<li><a href="/service-providers.html">Service Providers</a></li>
@@ -160,13 +142,9 @@
<li><a href="/ws-bpel-20.html">WS-BPEL 2.0</a></li>
<li><a href="/ws-i-basic-profile-11.html">WS-I Basic Profile 1.1</a></li>
<li><a href="/ws-security-in-ode.html">WS-Security in ODE</a></li>
-<li><a href="/wsdl-11-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.html">WSDL 1.1</a></li>
<li><a href="/xpath-10-expression-language.html">XPath 1.0 Expression Language</a></li>
<li><a href="/xpath-20-expression-language.html">XPath 2.0 Expression Language</a></li>
-<li><a href="/xpath-extensions.html">XPath Extensions</a></li>
-<li><a href="/xquery-extensions.html">XQuery Extensions</a></li>
</ul>
</div>
</div>
Modified: websites/staging/ode/trunk/content/soap-11.html
==============================================================================
--- websites/staging/ode/trunk/content/soap-11.html (original)
+++ websites/staging/ode/trunk/content/soap-11.html Fri Dec 28 13:13:46 2012
@@ -34,7 +34,7 @@
<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="/bpel-extensions.html">WS-BPEL Extensions</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>
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 Fri Dec 28 13:13:46 2012
@@ -34,7 +34,7 @@
<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="/bpel-extensions.html">WS-BPEL Extensions</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>
Modified: websites/staging/ode/trunk/content/specifications-and-standards.html
==============================================================================
--- websites/staging/ode/trunk/content/specifications-and-standards.html (original)
+++ websites/staging/ode/trunk/content/specifications-and-standards.html Fri Dec 28 13:13:46 2012
@@ -34,7 +34,7 @@
<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="/bpel-extensions.html">WS-BPEL Extensions</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>
Modified: websites/staging/ode/trunk/content/standard-faults.html
==============================================================================
--- websites/staging/ode/trunk/content/standard-faults.html (original)
+++ websites/staging/ode/trunk/content/standard-faults.html Fri Dec 28 13:13:46 2012
@@ -34,7 +34,7 @@
<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="/bpel-extensions.html">WS-BPEL Extensions</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>
Modified: websites/staging/ode/trunk/content/system-lifecycle.html
==============================================================================
--- websites/staging/ode/trunk/content/system-lifecycle.html (original)
+++ websites/staging/ode/trunk/content/system-lifecycle.html Fri Dec 28 13:13:46 2012
@@ -34,7 +34,7 @@
<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="/bpel-extensions.html">WS-BPEL Extensions</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>
Modified: websites/staging/ode/trunk/content/uninitializedvariable.html
==============================================================================
--- websites/staging/ode/trunk/content/uninitializedvariable.html (original)
+++ websites/staging/ode/trunk/content/uninitializedvariable.html Fri Dec 28 13:13:46 2012
@@ -34,7 +34,7 @@
<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="/bpel-extensions.html">WS-BPEL Extensions</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>
Modified: websites/staging/ode/trunk/content/uri.html
==============================================================================
--- websites/staging/ode/trunk/content/uri.html (original)
+++ websites/staging/ode/trunk/content/uri.html Fri Dec 28 13:13:46 2012
@@ -34,7 +34,7 @@
<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="/bpel-extensions.html">WS-BPEL Extensions</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>
Modified: websites/staging/ode/trunk/content/url.html
==============================================================================
--- websites/staging/ode/trunk/content/url.html (original)
+++ websites/staging/ode/trunk/content/url.html Fri Dec 28 13:13:46 2012
@@ -34,7 +34,7 @@
<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="/bpel-extensions.html">WS-BPEL Extensions</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>
Modified: websites/staging/ode/trunk/content/use-assign-to-build-messages.html
==============================================================================
--- websites/staging/ode/trunk/content/use-assign-to-build-messages.html (original)
+++ websites/staging/ode/trunk/content/use-assign-to-build-messages.html Fri Dec 28 13:13:46 2012
@@ -34,7 +34,7 @@
<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="/bpel-extensions.html">WS-BPEL Extensions</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>
Added: websites/staging/ode/trunk/content/userguide/activity-failure-and-recovery.html
==============================================================================
--- websites/staging/ode/trunk/content/userguide/activity-failure-and-recovery.html (added)
+++ websites/staging/ode/trunk/content/userguide/activity-failure-and-recovery.html Fri Dec 28 13:13:46 2012
@@ -0,0 +1,200 @@
+<!DOCTYPE html>
+<html>
+ <head>
+ <title>Activity Failure and Recovery</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=" 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>Activity Failure and Recovery</h1>
+
+ </div>
+ </header>
+
+
+ <!-- Content -->
+ <div class="container">
+
+ <div class="row">
+ <div class="span12">
+ <p>There are several types of error conditions. In this document we introduce a class of error condition called <em>failures</em>, distinct from <em>faults</em>, and describe how failures are caught and handled by the process engine.</p>
+<p>A service returns a fault in response to a request it cannot process. A process may also raise a fault internally when it encounters a terminal error condition, e.g. a faulty expression or false join condition. In addition, processes may raise faults in order to terminate normal processing.</p>
+<p>In contrast, failures are non-terminal error conditions that do not affect the normal flow of the process. We keep the process definition simple and straightforward by delegating failure handling to the process engine and administrator.</p>
+<p>For example, when the process is unable to perform DNS resolution to determine the service endpoint, it generates a failure. An administrator can fix the DNS server and tell the process engine to retry the activity. Had the DNS error been reported as a fault, the process would either terminate or require complex fault handling and recovery logic to proceed past this point of failure.</p>
+<p>In short, failures shields the process from common, non-terminal error conditions while retaining simple and straightforward process definitions that do not need to account for these error conditions.</p>
+<p><a name="ActivityFailureandRecovery-FromFailuretoRecovery"></a></p>
+<h3 id="from-failure-to-recovery">From Failure to Recovery</h3>
+<p>Currently, the <em>Invoke</em> activity is the only activity that supports failure handling and recovery. The mechanism is identical for all other activities that may support failure handling and recovery in the future.</p>
+<p>In case of the <em>Invoke</em> activity, a failure condition is triggered by the integration layer, in lieu of a response or fault message. The <em>Invoke</em> activity consults its failure handling policy (specified here) and decides how to respond.</p>
+<p>Set <em>faultOnFailure</em> to <em>yes</em>, if you want the activity to throw a fault on failure. All other failure handling settings are ignored. The activity will throw the <em>activityFailure</em> fault.</p>
+<p>The <em>activityFailure</em> fault is a standard fault, so you can use the <em>exitOnStandardFault</em> attribute to control whether the process exits immediately, or throws a fault in the enclosing scope.</p>
+<p>Set <em>retryFor</em> to a positive integer if you want the activity to attempt self-recovery and retry up to that number of times. Set <em>retryDelay</em> to a reasonable time delay (specified in seconds) between retries. For example, if you set <em>retryFor=2, retryDelay=30</em>, the activity will retry after 30 and 60 seconds, for a total of three attempts, before entering activity recovery mode.</p>
+<p>If the activity retries and succeeds, it will complete successfully as if no failure occurred. Of course, the activity may retry and fault, e.g. if the invoked service returns a fault. If the activity has exhausted all retry attempts, it enters activity recovery mode. By default <em>retryFor</em> is zero, and the activity enters recovery mode after the first failure.</p>
+<p>When in recovery mode, you can recover the activity in one of three ways:
+<em> </em>Retry<em> -- Retry the activity manually. You can repeat this any number of times until the activity completes or faults.
+</em> <em>Fault</em> -- Causes the activity to throw the <em>activityFailure</em> fault.
+<em> </em>Cancel* -- Cancels the activity. The activity completes unsuccessfully: without changing the state of variables, by setting the status of all its source links to false, and without installing a compensation handler.
+Activity recovery is performed individually for each activity instance, and does not affect other activities executing in the same process. While the activity is in the <em>FAILURE</em> state, the process instance remains in the <em>ACTIVE</em> state and may execute other activities from parallel flows and event handlers.</p>
+<p><a name="ActivityFailureandRecovery-SpecifyingFailureBehavior"></a></p>
+<h3 id="specifying-failure-behavior">Specifying Failure Behavior</h3>
+<p>Use the <em>failureHandling</em> extensibility element defined in the namespace <code>http://ode.apache.org/activityRecovery</code>. The structure of the <em>failureHandling</em> element is:</p>
+<div class="codehilite"><pre><span class="nt"><ext:failureHandling</span> <span class="na">xmlns:ext=</span><span class="s">"http://ode.apache.org/activityRecovery"</span><span class="nt">></span>
+ <span class="nt"><ext:faultOnFailure></span> _boolean_ <span class="nt"></ext:faultOnFailure></span>
+ <span class="nt"><ext:retryFor></span> _integer_ <span class="nt"></ext:retryFor></span>
+ <span class="nt"><ext:retryDelay></span> _integer_ <span class="nt"></ext:retryDelay></span>
+<span class="nt"></ext:failureHandling></span>
+</pre></div>
+
+
+<p>The <em>faultOnFailure</em>, <em>retryFor</em> and <em>retryDelay</em> elements are optional. The default values are false for <em>faultOnFailure</em>, and zero for <em>retryFor</em> and <em>retryDelay</em>.</p>
+<p>An activity that does not specify failure handling using this extensibility element, inherits the failure handling policy of its parent activity, recursively up to the top-level activity of the process. You can useinheritence to specify the failure handling policy of a set of activities, or all activities in the process, using a single <em>failureHandling</em> extensibility element.</p>
+<p>Note that due to this behavior, if activity <em>S</em> specifies failure handling with the values <em>retryFor=2, retryDelay=60</em>, and has a child activity <em>R</em> that specifies failure handling with the values <em>retryFor=3</em>, the <em>retryDelay</em> value for the child activity <em>R</em> is 0, and not 60. Using the <em>failureHandling</em> element without specifying one of its value elements will apply the default value for that element.</p>
+<p><a name="ActivityFailureandRecovery-Examples"></a></p>
+<h3 id="examples">Examples</h3>
+<p>A simple invoke with the <code>ext:failureHandling</code> extension:</p>
+<div class="codehilite"><pre><span class="nt"><bpel:invoke</span> <span class="na">inputVariable=</span><span class="s">"myRequest"</span>
+ <span class="na">operation=</span><span class="s">"foo"</span> <span class="na">outputVariable=</span><span class="s">"aResponse"</span>
+ <span class="na">partnerLink=</span><span class="s">"myPartner"</span> <span class="na">portType=</span><span class="s">"spt:SomePortType"</span><span class="nt">></span>
+
+ <span class="nt"><ext:failureHandling</span> <span class="na">xmlns:ext=</span><span class="s">"http://ode.apache.org/activityRecovery"</span><span class="nt">></span>
+ <span class="nt"><ext:faultOnFailure></span>false<span class="nt"></ext:faultOnFailure></span>
+ <span class="nt"><ext:retryFor></span>2<span class="nt"></ext:retryFor></span>
+ <span class="nt"><ext:retryDelay></span>60<span class="nt"></ext:retryDelay></span>
+ <span class="nt"></ext:failureHandling></span>
+
+<span class="nt"></bpel:invoke></span>
+</pre></div>
+
+
+<p>And a sequence activity that converts failures into faults:</p>
+<div class="codehilite"><pre><span class="nt"><bpel:sequence></span>
+
+ <span class="nt"><ext:failureHandling</span> <span class="na">xmlns:ext=</span><span class="s">"http://ode.apache.org/activityRecovery"</span><span class="nt">></span>
+ <span class="nt"><ext:faultOnFailure></span>true<span class="nt"></ext:faultOnFailure></span>
+ <span class="nt"></ext:failureHandling></span>
+
+ ...
+
+ <span class="nt"><bpel:invoke</span> <span class="na">inputVariable=</span><span class="s">"myRequest"</span>
+ <span class="na">operation=</span><span class="s">"foo"</span> <span class="na">outputVariable=</span><span class="s">"aResponse"</span>
+ <span class="na">partnerLink=</span><span class="s">"myPartner"</span> <span class="na">portType=</span><span class="s">"spt:SomePortType"</span><span class="nt">></span>
+
+ <span class="nt"><bpel:catchAll></span>
+ ...
+ <span class="nt"></bpel:catchAll></span>
+
+ <span class="nt"></bpel:invoke></span>
+
+<span class="nt"></bpel:sequence></span>
+</pre></div>
+
+
+<p><a name="ActivityFailureandRecovery-ProcessInstanceManagement"></a></p>
+<h3 id="process-instance-management">Process Instance Management</h3>
+<p>The process instance management provides the following information:
+<em> Process instance summary includes a <em>failures</em> element with a count of the total number of process instances that have one or more activities in recovery mode, and the date/time of the last activity to enter recovery mode. The element exists if at least one activity is in recovery mode.</em> Process instance information includes a <em>failures</em> element with a count of the number of activities in recovery mode, and the date/time of the last activity to enter recovery mode. The element exists if at least one activity is in recovery mode.
+* Activity instance information includes a <em>failure</em> element that specifies the date/time of the failure, the reason for the failure, number of retries, and list of available recovery actions. The element exists if the activity is in the state <em>FAILURE</em>.</p>
+<p>Use the <em>recoverActivity</em> operation to perform a recovery action on an activity in recovery mode. The operation requires the process instance ID, the activity instance ID and the recovery action to perform (one of retry, fault or cancel).</p>
+<p>You can also determine when failure or recovery occurred for a given activity instance from the execution log.</p>
+ </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
Added: websites/staging/ode/trunk/content/userguide/creating-a-process.html
==============================================================================
--- websites/staging/ode/trunk/content/userguide/creating-a-process.html (added)
+++ websites/staging/ode/trunk/content/userguide/creating-a-process.html Fri Dec 28 13:13:46 2012
@@ -0,0 +1,261 @@
+<!DOCTYPE html>
+<html>
+ <head>
+ <title>Creating a Process</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=" 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>Creating a Process</h1>
+
+ </div>
+ </header>
+
+
+ <!-- Content -->
+ <div class="container">
+
+ <div class="row">
+ <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="#deployment-descriptor">Deployment Descriptor</a></li>
+<li><a href="#formal-definition">Formal definition</a><ul>
+<li><a href="#examples">Examples</a></li>
+<li><a href="#additional-settings">Additional settings</a><ul>
+<li><a href="#in-memory-execution">In memory execution</a></li>
+<li><a href="#user-defined-process-properties">User-defined process properties</a></li>
+</ul>
+</li>
+</ul>
+</li>
+</ul>
+</div>
+<p><a name="CreatingaProcess-DeployingaProcessinOde"></a></p>
+<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><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><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>
+<div class="codehilite"><pre><span class="nt"><deploy></span>
+ <span class="nt"><process</span> <span class="err">...</span><span class="nt">></span>*
+ { other elements }
+ <span class="nt"></process></span>
+<span class="nt"></deploy></span>
+</pre></div>
+
+
+<p>Each process is identified by its qualified name and specifies bindings for provided and invoked services:</p>
+<div class="codehilite"><pre><span class="nt"><process</span> <span class="na">name =</span> <span class="s">QName</span> <span class="na">fileName =</span> <span class="s">String?</span> <span class="na">bpel11wsdlFileName =</span> <span class="s">String?</span> <span class="nt">></span>
+ (<span class="nt"><provide></span> | <span class="nt"><invoke></span>)*
+ { other elements }
+<span class="nt"></process></span>
+</pre></div>
+
+
+<p>Each process element must provide a <code>name</code> attribute with the qualified name of the process. Optionally, a <code>fileName</code> attribute can be used to specify the location of the BPEL process definition (the .bpel file). The <code>fileName</code> attribute does not need to be provided unless non-standard compilation options are used or the <code>bpel11wsdlFileName</code> attribute is used to specify a WSDL document for a BPEL 1.1 process. </p>
+<p>Each <code><process></code> element must enumerate the services provided by the process and bind each service to an endpoint. This is done through <code><provide></code> elements which associates <code>partnerLink</code>s with <code>endpoint</code>s:</p>
+<div class="codehilite"><pre><span class="nt"><provide</span> <span class="na">partnerLink=</span><span class="s">NCName</span><span class="nt">></span>
+ <span class="nt"><service</span> <span class="na">name =</span> <span class="s">QName</span> <span class="na">port =</span> <span class="s">NCName?</span><span class="nt">></span>
+<span class="nt"></provide></span>
+</pre></div>
+
+
+<p>Note, that only one partnerLink can be bound to any specified endpoint.</p>
+<p>The port attribute can be used to select a particular endpoint from the service definition.</p>
+<p><a name="CreatingaProcess-Examples"></a></p>
+<h4 id="examples">Examples</h4>
+<p>A very simple process that would only be invoked would use a deploy.xml very similar to:</p>
+<div class="codehilite"><pre><span class="nt"><deploy</span> <span class="na">xmlns=</span><span class="s">"http://www.apache.org/ode/schemas/dd/2007/03"</span>
+ <span class="na">xmlns:pns=</span><span class="s">"http://ode/bpel/unit-test"</span> <span class="na">xmlns:wns=</span><span class="s">"http://ode/bpel/unit-test.wsdl"</span><span class="nt">></span>
+ <span class="nt"><process</span> <span class="na">name=</span><span class="s">"pns:HelloWorld2"</span><span class="nt">></span>
+ <span class="nt"><active></span>true<span class="nt"></active></span>
+ <span class="nt"><provide</span> <span class="na">partnerLink=</span><span class="s">"helloPartnerLink"</span><span class="nt">></span>
+ <span class="nt"><service</span> <span class="na">name=</span><span class="s">"wns:HelloService"</span> <span class="na">port=</span><span class="s">"HelloPort"</span><span class="nt">/></span>
+ <span class="nt"></provide></span>
+ <span class="nt"></process></span>
+<span class="nt"></deploy></span>
+</pre></div>
+
+
+<p>See the complete example <a href="https://svn.apache.org/repos/asf/ode/trunk/distro-axis2/src/examples/HelloWorld2/">here</a>.</p>
+<p>A deployment including two processes invoking each other and whose execution would be triggered by a first message would look like:</p>
+<div class="codehilite"><pre><span class="nt"><deploy</span> <span class="na">xmlns=</span><span class="s">"http://www.apache.org/ode/schemas/dd/2007/03"</span> <span class="na">xmlns:main=</span><span class="s">"http://ode/bpel/unit-test"</span>
+ <span class="na">xmlns:mws=</span><span class="s">"http://ode/bpel/unit-test.wsdl"</span> <span class="na">xmlns:resp=</span><span class="s">"http://ode/bpel/responder"</span><span class="nt">></span>
+
+ <span class="nt"><process</span> <span class="na">name=</span><span class="s">"main:MagicSessionMain"</span><span class="nt">></span>
+ <span class="nt"><provide</span> <span class="na">partnerLink=</span><span class="s">"executePartnerLink"</span><span class="nt">></span>
+ <span class="nt"><service</span> <span class="na">name=</span><span class="s">"mws:MSMainExecuteService"</span> <span class="na">port=</span><span class="s">"MSExecutePort"</span><span class="nt">/></span>
+ <span class="nt"></provide></span>
+ <span class="nt"><provide</span> <span class="na">partnerLink=</span><span class="s">"responderPartnerLink"</span><span class="nt">></span>
+ <span class="nt"><service</span> <span class="na">name=</span><span class="s">"mws:MSMainService"</span> <span class="na">port=</span><span class="s">"MSMainPort"</span><span class="nt">/></span>
+ <span class="nt"></provide></span>
+ <span class="nt"><invoke</span> <span class="na">partnerLink=</span><span class="s">"responderPartnerLink"</span><span class="nt">></span>
+ <span class="nt"><service</span> <span class="na">name=</span><span class="s">"mws:MSResponderService"</span> <span class="na">port=</span><span class="s">"MSResponderPort"</span><span class="nt">/></span>
+ <span class="nt"></invoke></span>
+ <span class="nt"></process></span>
+ <span class="nt"><process</span> <span class="na">name=</span><span class="s">"resp:MagicSessionResponder"</span><span class="nt">></span>
+ <span class="nt"><type></span>resp:MagicSessionResponder<span class="nt"></type></span>
+ <span class="nt"><provide</span> <span class="na">partnerLink=</span><span class="s">"mainPartnerLink"</span><span class="nt">></span>
+ <span class="nt"><service</span> <span class="na">name=</span><span class="s">"mws:MSResponderService"</span> <span class="na">port=</span><span class="s">"MSResponderPort"</span><span class="nt">/></span>
+ <span class="nt"></provide></span>
+ <span class="nt"><invoke</span> <span class="na">partnerLink=</span><span class="s">"mainPartnerLink"</span><span class="nt">></span>
+ <span class="nt"><service</span> <span class="na">name=</span><span class="s">"mws:MSMainService"</span> <span class="na">port=</span><span class="s">"MSMainPort"</span><span class="nt">/></span>
+ <span class="nt"></invoke></span>
+ <span class="nt"></process></span>
+<span class="nt"></deploy></span>
+</pre></div>
+
+
+<p>See the complete example <a href="https://svn.apache.org/repos/asf/ode/trunk/distro-axis2/src/examples/MagicSession/">here</a>.</p>
+<p><a name="CreatingaProcess-Additionalsettings"></a></p>
+<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>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>
+ <span class="nt"><provide</span> <span class="na">partnerLink=</span><span class="s">"helloPartnerLink"</span><span class="nt">></span>
+ <span class="nt"><service</span> <span class="na">name=</span><span class="s">"wns:HelloService"</span> <span class="na">port=</span><span class="s">"HelloPort"</span><span class="nt">/></span>
+ <span class="nt"></provide></span>
+<span class="nt"></process></span>
+</pre></div>
+
+
+<p>Be aware that in-memory executions introduces many restrictions on your process and what it can do. The instances of these processes can't be queried by using the <a href="management-api.html">Management API</a>. The process definition can only include one single receive activity (the one that will trigger the instance creation).</p>
+<p><a name="CreatingaProcess-User-definedprocessproperties"></a></p>
+<h5 id="user-defined-process-properties">User-defined process properties</h5>
+<p>User-defined process properties provide means to configure process models and their instances. They are either statically declared and set in the deployment descriptor <code>deploy.xml</code> or can be set using the process management API. All instances of a process model share the same set of process properties. If a process property changes, it changes for all instances.</p>
+<p>A process property is identified by a QName and can carry a string as value. To set a process property statically in the deployment descriptor, add the following snippet to your <code>deploy.xml</code>:</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"><property</span> <span class="na">xmlns:loan=</span><span class="s">"urn:example"</span> <span class="na">name=</span><span class="s">"loan:loanThreshold"</span><span class="nt">></span>4711<span class="nt"></property></span>
+ ...
+<span class="nt"></process></span>
+</pre></div>
+
+
+<p>It is also possible to set or change a property by calling the PM API function <code>setProcessProperty(final QName pid, final QName propertyName, final String value)</code>.</p>
+<p>Once set, process properties can be used in two different ways:
+ * Using XPath in process models
+ * Using Java in ODE extensions</p>
+<p>For instance, instead of hard coding the amount of money that triggers an in-depth check in a loan approval process, you could read a process property instead. That way you can reconfigure your process without having to redeploy the process again.</p>
+<p>To read process properties in a BPEL process, you can use the non-standard XPath extension <code>bpws:process-property(propertyName)</code>, e.g. in a transition condition or in an assign activity:</p>
+<div class="codehilite"><pre>...
+<span class="nt"><assign></span>
+ <span class="nt"><copy></span>
+ <span class="nt"><from</span> <span class="na">xmlns:loan=</span><span class="s">"urn:example"</span><span class="nt">></span>bpws:process-property(loan:loanThreshold)<span class="nt"></from></span>
+ <span class="nt"><to></span><span class="p">$</span><span class="nv">threshold</span><span class="nt"></to></span>
+ <span class="nt"></copy></span>
+<span class="nt"></assign></span>
+...
+</pre></div>
+ </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
Added: websites/staging/ode/trunk/content/userguide/direct-process-to-process-communication.html
==============================================================================
--- websites/staging/ode/trunk/content/userguide/direct-process-to-process-communication.html (added)
+++ websites/staging/ode/trunk/content/userguide/direct-process-to-process-communication.html Fri Dec 28 13:13:46 2012
@@ -0,0 +1,122 @@
+<!DOCTYPE html>
+<html>
+ <head>
+ <title>Direct Process-to-Process Communication</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=" 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>Direct Process-to-Process Communication</h1>
+
+ </div>
+ </header>
+
+
+ <!-- Content -->
+ <div class="container">
+
+ <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>
+ </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
Added: websites/staging/ode/trunk/content/userguide/endpoint-references.html
==============================================================================
--- websites/staging/ode/trunk/content/userguide/endpoint-references.html (added)
+++ websites/staging/ode/trunk/content/userguide/endpoint-references.html Fri Dec 28 13:13:46 2012
@@ -0,0 +1,267 @@
+<!DOCTYPE html>
+<html>
+ <head>
+ <title>Endpoint References</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=" 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>Endpoint References</h1>
+
+ </div>
+ </header>
+
+
+ <!-- Content -->
+ <div class="container">
+
+ <div class="row">
+ <div class="span12">
+ <p><a name="EndpointReferences-Introduction"></a></p>
+<h3 id="introduction">Introduction</h3>
+<p>An endpoint reference holds information to call a service. The simplest endpoint reference is usually an URL but it can also be much more complex such as holding a message id, a reply-to address or custom properties.</p>
+<p>In BPEL, endpoint references (aka EPRs) are modeled as partner link roles. When defining a partner link, two roles maybe defined, <code>myRole</code> and <code>partnerRole</code>:</p>
+<div class="codehilite"><pre><span class="o"><</span><span class="n">partnerLink</span> <span class="n">name</span><span class="o">=</span><span class="s">"responderPartnerLink"</span> <span class="n">partnerLinkType</span><span class="o">=</span><span class="s">"test:ResponderPartnerLinkType"</span>
+ <span class="n">myRole</span><span class="o">=</span><span class="s">"main"</span> <span class="n">partnerRole</span><span class="o">=</span><span class="s">"responder"</span> <span class="n">initializePartnerRole</span><span class="o">=</span><span class="s">"yes"</span><span class="o">/></span>
+</pre></div>
+
+
+<p>Both <code>partnerRole</code> and <code>myRole</code> represent EPRs. So when assigning partner link roles or invoking partners, you are using EPRs behind the scene.</p>
+<p><a name="EndpointReferences-ODEandEndpointReferences"></a></p>
+<h3 id="ode-and-endpoint-references">ODE and Endpoint References</h3>
+<p><a name="EndpointReferences-TypesofEPRs"></a></p>
+<h4 id="types-of-eprs">Types of EPRs</h4>
+<p>The ODE runtime supports 4 types of EPRs:</p>
+<ul>
+<li>A simple URL or a URL in the location attribute of the binding. See <a href="http://www.w3.org/TR/wsdl#_soap:address">soap:address</a> and <a href="http://www.w3.org/TR/wsdl#_http:address">http:address</a> WSDL 1.1 binding.</li>
+<li>A <a href="http://www.w3.org/TR/ws-addr-core/">WS-Addressing</a> <a href="http://www.w3.org/TR/ws-addr-core/#eprinfomodel">EndpointReference</a>.</li>
+<li>A <a href="http://www.w3.org/TR/wsdl">WSDL 1.1</a> <a href="http://www.w3.org/TR/wsdl#_services">service element</a>.</li>
+<li>A <a href="http://www.w3.org/TR/wsdl20/">WSDL 2.0</a> <a href="http://www.w3.org/TR/wsdl20/#Endpoint">endpoint element</a>.</li>
+</ul>
+<p>We recommend the two first solutions to interact with the engine. The first one is just the easiest and for the case where you need more robustness, WS-Addressing is the most popular second choice.</p>
+<p>To show you how these EPRs look like and how they can be assigned to partner links roles here are some examples:</p>
+<div class="codehilite"><pre><span class="nt"><assign></span>
+
+ <span class="c"><!-- Simple URL, without the wrapper --></span>
+ <span class="nt"><copy></span>
+ <span class="nt"><from></span>
+ <span class="nt"><literal></span>http://localhost:8080/ode/dynresponder<span class="nt"></literal></span>
+ <span class="nt"></from></span>
+ <span class="nt"><to</span> <span class="na">partnerLink=</span><span class="s">"responderPartnerLink"</span><span class="nt">/></span>
+ <span class="nt"></copy></span>
+
+ <span class="c"><!-- Simple URL, wrapped in an soap:address element --></span>
+ <span class="nt"><copy></span>
+ <span class="nt"><from></span>
+ <span class="nt"><literal></span>
+ <span class="nt"><service-ref></span>
+ <span class="nt"><soap:address</span> <span class="na">location=</span><span class="s">"http://localhost:8080/ode/dynresponder"</span><span class="nt">/></span>
+ <span class="nt"></service-ref></span>
+ <span class="nt"></literal></span>
+ <span class="nt"></from></span>
+ <span class="nt"><to</span> <span class="na">partnerLink=</span><span class="s">"responderPartnerLink"</span><span class="nt">/></span>
+ <span class="nt"></copy></span>
+
+ <span class="c"><!-- WS-Addressing EPR, without the wrapper --></span>
+ <span class="nt"><copy></span>
+ <span class="nt"><from></span>
+ <span class="nt"><literal></span>
+ <span class="nt"><wsa:EndpointReference</span> <span class="na">xmlns:wsa=</span><span class="s">"http://www.w3.org/2005/08/addressing"</span><span class="nt">></span>
+ <span class="nt"><wsa:To></span>http://localhost:8080/ode/dynresponder<span class="nt"></wsa:To></span>
+ <span class="nt"></wsa:EndpointReference></span>
+ <span class="nt"></literal></span>
+ <span class="nt"></from></span>
+ <span class="nt"><to</span> <span class="na">partnerLink=</span><span class="s">"responderPartnerLink"</span><span class="nt">/></span>
+ <span class="nt"></copy></span>
+
+ <span class="c"><!-- WS-Addressing EPR, with the wrapper --></span>
+ <span class="nt"><copy></span>
+ <span class="nt"><from></span>
+ <span class="nt"><literal></span>
+ <span class="nt"><service-ref></span>
+ <span class="nt"><wsa:EndpointReference</span> <span class="na">xmlns:wsa=</span><span class="s">"http://www.w3.org/2005/08/addressing"</span><span class="nt">></span>
+ <span class="nt"><wsa:To></span>http://localhost:8080/ode/dynresponder<span class="nt"></wsa:To></span>
+ <span class="nt"></wsa:EndpointReference></span>
+ <span class="nt"><service-ref></span>
+ <span class="nt"></literal></span>
+ <span class="nt"></from></span>
+ <span class="nt"><to</span> <span class="na">partnerLink=</span><span class="s">"responderPartnerLink"</span><span class="nt">/></span>
+ <span class="nt"></copy></span>
+
+ <span class="c"><!-- WSDL1.1 EPR, without the wrapper --></span>
+ <span class="nt"><copy></span>
+ <span class="nt"><from></span>
+ <span class="nt"><literal></span>
+ <span class="nt"><wsdl:service</span> <span class="na">xmlns:wsdl=</span><span class="s">"http://schemas.xmlsoap.org/wsdl/"</span> <span class="na">name=</span><span class="s">"DynService"</span> <span class="na">targetNamespace=</span><span class="s">"http://org.apache.ode/examples/dynservice"</span><span class="nt">></span>
+ <span class="nt"><wsdl:port</span> <span class="na">name=</span><span class="s">"DynPort"</span><span class="nt">></span>
+ <span class="nt"><soap:address</span> <span class="na">location=</span><span class="s">"http://localhost:8080/ode/dynresponder"</span><span class="nt">/></span>
+ <span class="nt"></wsdl:port></span>
+ <span class="nt"></wsdl:service></span>
+ <span class="nt"></literal></span>
+ <span class="nt"></from></span>
+ <span class="nt"><to</span> <span class="na">partnerLink=</span><span class="s">"responderPartnerLink"</span><span class="nt">/></span>
+ <span class="nt"></copy></span>
+
+ <span class="c"><!-- WSDL2.0 EPR, with the wrapper --></span>
+ <span class="nt"><copy></span>
+ <span class="nt"><from></span>
+ <span class="nt"><literal></span>
+ <span class="nt"><service-ref></span>
+ <span class="nt"><wsdl:service</span> <span class="na">xmlns:wsdl=</span><span class="s">"http://www.w3.org/2006/01/wsdl"</span> <span class="na">name=</span><span class="s">"DynService"</span> <span class="na">targetNamespace=</span><span class="s">"http://org.apache.ode/examples/dynservice"</span><span class="nt">></span>
+ <span class="nt"><wsdl:port</span> <span class="na">name=</span><span class="s">"DynPort"</span><span class="nt">></span>
+ <span class="nt"><soap:address</span> <span class="na">location=</span><span class="s">"http://localhost:8080/ode/dynresponder"</span><span class="nt">/></span>
+ <span class="nt"></wsdl:port></span>
+ <span class="nt"></wsdl:service></span>
+ <span class="nt"></service-ref></span>
+ <span class="nt"></literal></span>
+ <span class="nt"></from></span>
+ <span class="nt"><to</span> <span class="na">partnerLink=</span><span class="s">"responderPartnerLink"</span><span class="nt">/></span>
+ <span class="nt"></copy></span>
+
+<span class="nt"></assign></span>
+</pre></div>
+
+
+<p>Normally BPEL requires wrapping EPRs with inside a <code>service-ref</code> element, however ODE relaxes this requirement for ease of use and increased interoperability with existing services. If the <code>service-ref</code> element is absent, the EPR is automatically wrapped inside one on the fly. Moreover, ODE automatically detects the different EPR types when assigning to a partner link role. If you need to use WS-Addressing sessions (@see appropriate page), then you will have to use <code>wsa:EndpointReference</code> EPRs.</p>
+<p>You can just as well assign EPRs to/from variables to pass them around and enable more dynamic communication patterns.</p>
+<p><a name="EndpointReferences-PassingEndpointReferences"></a></p>
+<h3 id="passing-endpoint-references">Passing Endpoint References</h3>
+<p>To pass endpoint references around and manipulate them, you usually need to assigne them to variables. The EPR can then be sent in a message and reassigned to another partner link. This lets you model complex scenarii where you don't know the address of your partner beforehand or where you select one partner among many others.</p>
+<p>The type of the variable that will hold your EPR defines the type of the EPR that it will contain. For example if you define a message in your WSDL document that looks like this:</p>
+<div class="codehilite"><pre><span class="nt"><wsdl:message</span> <span class="na">name=</span><span class="s">"EndpointMessage"</span><span class="nt">></span>
+ <span class="nt"><wsdl:part</span> <span class="na">name=</span><span class="s">"payload"</span> <span class="na">element=</span><span class="s">"xsd:string"</span><span class="nt">/></span>
+<span class="nt"></wsdl:message></span>
+</pre></div>
+
+
+<p>ODE will automatically put a simple URL EPR when you assign this message part:</p>
+<div class="codehilite"><pre><span class="nt"><variable</span> <span class="na">name=</span><span class="s">"myEndpoint"</span> <span class="na">messageType=</span><span class="s">"resp:EndpointMessage"</span><span class="nt">/></span>
+...
+<span class="nt"><assign></span>
+ <span class="nt"><copy></span>
+ <span class="nt"><from</span> <span class="na">partnerLink=</span><span class="s">"mainPartnerLink"</span> <span class="na">endpointReference=</span><span class="s">"myRole"</span><span class="nt">/></span>
+ <span class="nt"><to</span> <span class="na">variable=</span><span class="s">"myEndpoint"</span> <span class="na">part=</span><span class="s">"payload"</span><span class="nt">/></span>
+ <span class="nt"></copy></span>
+<span class="nt"></assign></span>
+</pre></div>
+
+
+<p>Now if you want to manipulate a WS-Addressing EPR, the only thing you have to change in the above examples is the message part type. So your message will then look like this:</p>
+<p><wsdl:message name="EndpointMessage">
+ <wsdl:part name="payload" element="wsa:EndpointReference"/>
+</wsdl:message></p>
+<p>Once your EPR has been assigned to a variable and set, say, to another process, you just need to reassign it to a partner link <code>partnerRole</code> to use it:</p>
+<div class="codehilite"><pre><span class="nt"><assign></span>
+ <span class="nt"><copy></span>
+ <span class="nt"><from</span> <span class="na">variable=</span><span class="s">"eprmessage"</span> <span class="na">part=</span><span class="s">"payload"</span><span class="nt">/></span>
+ <span class="nt"><to</span> <span class="na">partnerLink=</span><span class="s">"mainPartnerLink"</span><span class="nt">/></span>
+ <span class="nt"></copy></span>
+<span class="nt"></assign></span>
+<span class="nt"><invoke</span> <span class="na">name=</span><span class="s">"eprcall"</span> <span class="na">partnerLink=</span><span class="s">"mainPartnerLink"</span>
+ <span class="na">portType=</span><span class="s">"resp:MSMainPortType"</span> <span class="na">operation=</span><span class="s">"call"</span> <span class="na">inputVariable=</span><span class="s">"eprmessage"</span><span class="nt">/></span>
+</pre></div>
+
+
+<p>For a complete example check <a href="http://svn.apache.org/repos/asf/ode/trunk/distro/src/examples-war/DynPartner/">DynPartner</a> in the engine examples.</p>
+ </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/userguide/index.html
==============================================================================
--- websites/staging/ode/trunk/content/userguide/index.html (original)
+++ websites/staging/ode/trunk/content/userguide/index.html Fri Dec 28 13:13:46 2012
@@ -34,7 +34,7 @@
<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="/bpel-extensions.html">WS-BPEL Extensions</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>
@@ -112,7 +112,7 @@
<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="bpel-extensions.html">BPEL Extensions</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>
<li><a href="stateful-exchange-protocol.html">Stateful Exchange Protocol</a></li>