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 [5/6] - in /websites/staging/ode/trunk/content: ./
developerguide/ extensions/ userguide/
Added: websites/staging/ode/trunk/content/userguide/instance-data-cleanup.html
==============================================================================
--- websites/staging/ode/trunk/content/userguide/instance-data-cleanup.html (added)
+++ websites/staging/ode/trunk/content/userguide/instance-data-cleanup.html Fri Dec 28 13:13:46 2012
@@ -0,0 +1,263 @@
+<!DOCTYPE html>
+<html>
+ <head>
+ <title>Instance Data Cleanup</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>Instance Data Cleanup</h1>
+
+ </div>
+ </header>
+
+
+ <!-- Content -->
+ <div class="container">
+
+ <div class="row">
+ <div class="span12">
+ <p><a name="InstanceDataCleanup-Rational"></a></p>
+<h2 id="rational">Rational</h2>
+<p>During its execution, a process instance can accumulate a significant amount of data. The running process itself isn't that much of an issue, when the instance is done there's nothing left to execute. But the process data can be rather big, mostly because of the messages it received and sent and its own variables. All of these are XML documents and in some cases, sizable ones.</p>
+<p><a name="InstanceDataCleanup-Levelsofcleanup"></a></p>
+<h2 id="levels-of-cleanup">Levels of cleanup</h2>
+<p><a name="InstanceDataCleanup-Cleanuponcompletion"></a></p>
+<h3 id="cleanup-on-completion">Cleanup on completion</h3>
+<p>{panel}
+This feature is only available in ODE 1.3 or later
+{panel}</p>
+<p>The easiest approach to get started is simply to wait until the instance execution is finished and then cleanup everything that's related to it. That would include the instance state with its variables, scopes and correlation, but also all the messages it has received and sent. Execution events should also be disposed of. So this description defines 5 different categories: instance, messages and events. We should be able to turn on and off each level separately.</p>
+<ul>
+<li>instance: ODE_PROCESS_INSTANCE, EXECUTION_STATE</li>
+<li>variables: ODE_SCOPE, ODE_XML_DATA, ODE_PARTNER_LINK</li>
+<li>messages: ODE_MESSAGE, ODE_MESSAGE_ROUTE, ODE_MEX_PROPS, ODE_MESSAGE_EXCHANGE</li>
+<li>correlations: ODE_CORRELATION_SET, ODE_CORSET_PROP</li>
+<li>events: ODE_EVENTS</li>
+</ul>
+<p><a name="InstanceDataCleanup-dtd"></a></p>
+<h4 id="dtd">dtd</h4>
+<div class="codehilite"><pre> <span class="nt"><xs:element</span> <span class="na">name=</span><span class="s">"cleanup"</span> <span class="na">minOccurs=</span><span class="s">"0"</span> <span class="na">maxOccurs=</span><span class="s">"3"</span> <span class="na">type=</span><span class="s">"dd:tCleanup"</span> <span class="nt">/></span>
+
+ <span class="nt"><xs:complexType</span> <span class="na">name=</span><span class="s">"tCleanup"</span><span class="nt">></span>
+ <span class="nt"><xs:sequence></span>
+ <span class="nt"><xs:element</span> <span class="na">name=</span><span class="s">"category"</span> <span class="na">default=</span><span class="s">"all"</span> <span class="na">minOccurs=</span><span class="s">"0"</span> <span class="na">maxOccurs=</span><span class="s">"unbounded"</span><span class="nt">></span>
+ <span class="nt"><xs:simpleType></span>
+ <span class="nt"><xs:restriction</span> <span class="na">base=</span><span class="s">"xs:string"</span><span class="nt">></span>
+ <span class="nt"><xs:enumeration</span> <span class="na">value=</span><span class="s">"instance"</span> <span class="nt">/></span>
+ <span class="nt"><xs:enumeration</span> <span class="na">value=</span><span class="s">"variables"</span> <span class="nt">/></span>
+ <span class="nt"><xs:enumeration</span> <span class="na">value=</span><span class="s">"messages"</span> <span class="nt">/></span>
+ <span class="nt"><xs:enumeration</span> <span class="na">value=</span><span class="s">"correlations"</span> <span class="nt">/></span>
+ <span class="nt"><xs:enumeration</span> <span class="na">value=</span><span class="s">"events"</span> <span class="nt">/></span>
+ <span class="nt"><xs:enumeration</span> <span class="na">value=</span><span class="s">"all"</span> <span class="nt">/></span>
+ <span class="nt"></xs:restriction></span>
+ <span class="nt"></xs:simpleType></span>
+ <span class="nt"></xs:element></span>
+ <span class="nt"></xs:sequence></span>
+ <span class="nt"><xs:attribute</span> <span class="na">name=</span><span class="s">"on"</span> <span class="na">use=</span><span class="s">"required"</span><span class="nt">></span>
+ <span class="nt"><xs:simpleType></span>
+ <span class="nt"><xs:restriction</span> <span class="na">base=</span><span class="s">"xs:string"</span><span class="nt">></span>
+ <span class="nt"><xs:enumeration</span> <span class="na">value=</span><span class="s">"success"</span> <span class="nt">/></span>
+ <span class="nt"><xs:enumeration</span> <span class="na">value=</span><span class="s">"failure"</span> <span class="nt">/></span>
+ <span class="nt"><xs:enumeration</span> <span class="na">value=</span><span class="s">"always"</span> <span class="nt">/></span>
+ <span class="nt"></xs:restriction></span>
+ <span class="nt"></xs:simpleType></span>
+ <span class="nt"></xs:attribute></span>
+ <span class="nt"></xs:complexType></span>
+</pre></div>
+
+
+<p><a name="InstanceDataCleanup-examples"></a></p>
+<h4 id="examples">examples</h4>
+<ol>
+<li>
+<p>no instance data cleanup</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"><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>
+</pre></div>
+
+
+</li>
+<li>
+<p>cleaning up all data on either successful or faulty completions of instances</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"><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"><cleanup</span> <span class="na">on=</span><span class="s">"always"</span> <span class="nt">/></span>
+<span class="nt"></process></span>
+</pre></div>
+
+
+</li>
+<li>
+<p>cleaning up all data on successful completions of instances and no data cleanup on faulty completions</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"><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"><cleanup</span> <span class="na">on=</span><span class="s">"success"</span> <span class="nt">></span>
+ <span class="nt"><category></span>instance<span class="nt"></category></span>
+ <span class="nt"><category></span>variables<span class="nt"></category></span>
+ <span class="nt"><category></span>messages<span class="nt"></category></span>
+ <span class="nt"><category></span>correlations<span class="nt"></category></span>
+ <span class="nt"><category></span>events<span class="nt"></category></span>
+ <span class="nt"></cleanup></span>
+<span class="nt"></process></span>
+</pre></div>
+
+
+</li>
+<li>
+<p>cleaning up all data on successful completions of instances and only messages and correlations on faulty completions</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"><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"><cleanup</span> <span class="na">on=</span><span class="s">"success"</span> <span class="nt">></span>
+ <span class="nt"><category></span>all<span class="nt"></category></span>
+ <span class="nt"></cleanup></span>
+ <span class="nt"><cleanup</span> <span class="na">on=</span><span class="s">"failure"</span><span class="nt">></span>
+ <span class="nt"><category></span>messages<span class="nt"></category></span>
+ <span class="nt"><category></span>correlations<span class="nt"></category></span>
+ <span class="nt"></cleanup></span>
+<span class="nt"></process></span>
+</pre></div>
+
+
+</li>
+<li>
+<p>an +invalid+ configuration; the instance category should accompany the variable and correlations categories</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"><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"><cleanup</span> <span class="na">on=</span><span class="s">"success"</span> <span class="nt">></span>
+ <span class="nt"><category></span>all<span class="nt"></category></span>
+ <span class="nt"></cleanup></span>
+ <span class="nt"><cleanup</span> <span class="na">on=</span><span class="s">"failure"</span><span class="nt">></span>
+ <span class="nt"><category></span>instance<span class="nt"></category></span>
+ <span class="nt"></cleanup></span>
+<span class="nt"></process></span>
+</pre></div>
+
+
+</li>
+</ol>
+<p><a name="InstanceDataCleanup-FutureDevelopments"></a></p>
+<h3 id="future-developments">Future Developments</h3>
+<p>WS-BPEL makes heavy use of scopes, those could be another hook in the execution lifecycle for the cleanup to take place. So instead of waiting until the instance is finished and clean up the whole state, we could proceed by smaller increments and delete the state scope by scope. For short running processes (say less than a few days) the advantages of this approach are minimal but for long running processes (say months), there's potentially a lot of unused state that's just sitting there and will never be used anymore.</p>
+<p><a name="InstanceDataCleanup-Finalnotes"></a></p>
+<h2 id="final-notes">Final notes</h2>
+<p>When we continue along the lines of refining further when the cleanup should occur and what exactly should be cleaned up, we quickly start getting close to the transaction boundaries. Down the road, ideally, we shouldn't persist anything unnecessarily, so that no cleanup is needed when a given piece of data will never be reused. It's often the case for message variables for example, where a process will receive a message, assign some values from it and never use that message variable anymore. So this should never get written, minimizing the writes and deletes.</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/instance-replayer.html
==============================================================================
--- websites/staging/ode/trunk/content/userguide/instance-replayer.html (added)
+++ websites/staging/ode/trunk/content/userguide/instance-replayer.html Fri Dec 28 13:13:46 2012
@@ -0,0 +1,229 @@
+<!DOCTYPE html>
+<html>
+ <head>
+ <title>Instance Replayer</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>Instance Replayer</h1>
+
+ </div>
+ </header>
+
+
+ <!-- Content -->
+ <div class="container">
+
+ <div class="row">
+ <div class="span12">
+ <p><a name="InstanceReplayer-Introduction"></a></p>
+<h2 id="introduction">Introduction</h2>
+<p>With instance replayer, you are able to upgrade long running process instance to the newest version.</p>
+<p>There's an ongoing discussion on apache.org in a feature request:</p>
+<p><a href="https://issues.apache.org/jira/browse/ODE-483">https://issues.apache.org/jira/browse/ODE-483</a>.</p>
+<p><a name="InstanceReplayer-Example"></a></p>
+<h2 id="example">Example</h2>
+<p>Attached are example service assembly <a href="^replayer-example-sa.zip.html">^replayer-example-sa.zip</a> and SoapUI project [^replayer-example-soapui-project.xml].</p>
+<p><a name="InstanceReplayer-Usage"></a></p>
+<h2 id="usage">Usage</h2>
+<p>The basic use cases for replayer are:</p>
+<ol>
+<li>migrate existing log running instances to newest process version given their communication (incoming and outgoing requests)</li>
+<li>reproduce error scenarios between two instances of ODE (eg. production and development)</li>
+</ol>
+<p>Replayer extends management api by 2 operations: replay and getCommunication (see pmapi.wsdl from ODE distribution).</p>
+<p>In order to do 1, you invoke:</p>
+<div class="codehilite"><pre> <span class="nt"><pmap:replay</span> <span class="na">xmlns:ns=</span><span class="s">"http://www.apache.org/ode/pmapi/types/2006/08/02/"</span><span class="nt">></span>
+ <span class="nt"><replay></span>
+ <span class="nt"><ns:upgradeInstance></span>1234<span class="nt"></ns:upgradeInstance></span>
+ <span class="nt"></replay></span>
+ <span class="nt"></pmap:replay></span>
+</pre></div>
+
+
+<p>To do 2, you need to retrieve exchanges from instance (or instances) by:</p>
+<div class="codehilite"><pre> <span class="nt"><pmap:getCommunication</span> <span class="na">xmlns:ns=</span><span class="s">"http://www.apache.org/ode/pmapi/types/2006/08/02/"</span><span class="nt">></span>
+ <span class="nt"><getCommunication></span>
+ <span class="nt"><ns:iid></span>1234<span class="nt"></ns:iid></span>
+ <span class="nt"></getCommunication></span>
+ <span class="nt"></pmap:getCommunication></span>
+
+ <span class="nt"><ns:restoreInstance></span>
+ <span class="nt"><ns:processType</span> <span class="na">xmlns:p=</span><span class="s">"http://sample.bpel.org/bpel/sample"</span><span class="nt">></span>p:OnEventCorrelation<span class="nt"></ns:processType></span>
+ <span class="nt"><exchange</span> <span class="na">xmlns=</span><span class="s">"http://www.apache.org/ode/pmapi/types/2006/08/02/"</span><span class="nt">></span>
+ <span class="nt"><type></span>M<span class="nt"></type></span>
+ <span class="nt"><createTime></span>2009-04-01T16:41:29.873+02:00<span class="nt"></createTime></span>
+ <span class="nt"><service</span> <span class="na">xmlns:sam=</span><span class="s">"http://sample.bpel.org/bpel/sample"</span><span class="nt">></span>sam:OnEventCorrelationInit<span class="nt"></service></span>
+ <span class="nt"><operation></span>initiate<span class="nt"></operation></span>
+ <span class="nt"><in></span>
+ <span class="nt"><initiate</span> <span class="na">xmlns:sam=</span><span class="s">"http://sample.bpel.org/bpel/sample"</span> <span class="na">xmlns:soapenv=</span><span class="s">"http://schemas.xmlsoap.org/soap/envelope/"</span> <span class="na">xmlns=</span><span class="s">""</span><span class="nt">></span>
+ <span class="nt"><payload></span>abc7<span class="nt"></payload></span>
+ <span class="nt"><payload2></span>abc8<span class="nt"></payload2></span>
+ <span class="nt"></initiate></span>
+ <span class="nt"></in></span>
+ <span class="nt"><out></span>
+ <span class="nt"><message</span> <span class="na">xmlns=</span><span class="s">""</span><span class="nt">></span>
+ <span class="nt"><payload></span>test1<span class="nt"></payload></span>
+ <span class="nt"><payload2/></span>
+ <span class="nt"></message></span>
+ <span class="nt"></out></span>
+ <span class="nt"></exchange></span>
+
+ <span class="nt"><exchange</span> <span class="na">xmlns:ns=</span><span class="s">"http://www.apache.org/ode/pmapi/types/2006/08/02/"</span> <span class="na">xmlns=</span><span class="s">"http://www.apache.org/ode/pmapi/types/2006/08/02/"</span><span class="nt">></span>
+ <span class="nt"><type></span>P<span class="nt"></type></span>
+ <span class="nt"><createTime></span>2009-04-01T16:41:32.998+02:00<span class="nt"></createTime></span>
+ <span class="nt"><service</span> <span class="na">xmlns:sam=</span><span class="s">"http://sample.bpel.org/bpel/sample"</span><span class="nt">></span>sam:OnEventCorrelation<span class="nt"></service></span>
+ <span class="nt"><operation></span>initiate<span class="nt"></operation></span>
+ <span class="nt"><in></span>
+ <span class="nt"><initiate</span> <span class="na">xmlns:sam=</span><span class="s">"http://sample.bpel.org/bpel/sample"</span> <span class="na">xmlns:soapenv=</span><span class="s">"http://schemas.xmlsoap.org/soap/envelope/"</span> <span class="na">xmlns=</span><span class="s">""</span><span class="nt">></span>
+ <span class="nt"><payload></span>abc7<span class="nt"></payload></span>
+ <span class="nt"><payload2></span>abc8<span class="nt"></payload2></span>
+ <span class="nt"></initiate></span>
+ <span class="nt"></in></span>
+ <span class="nt"><out></span>
+ <span class="nt"><message</span> <span class="na">xmlns=</span><span class="s">""</span><span class="nt">></span>
+ <span class="nt"><payload></span>test5<span class="nt"></payload></span>
+ <span class="nt"><payload2/></span>
+ <span class="nt"></message></span>
+ <span class="nt"></out></span>
+ <span class="nt"></exchange></span>
+ <span class="nt"></ns:restoreInstance></span>
+</pre></div>
+
+
+<p>Then, you execute replay on the other ODE installation to replicate instance:</p>
+<div class="codehilite"><pre> <span class="nt"><pmap:replay</span> <span class="na">xmlns:ns=</span><span class="s">"http://www.apache.org/ode/pmapi/types/2006/08/02/"</span><span class="nt">></span>
+ <span class="nt"><replay></span>
+ <span class="nt"><ns:restoreInstance></span>
+ <span class="nt"><ns:processType</span> <span class="na">xmlns:p=</span><span class="s">"http://sample.bpel.org/bpel/sample"</span><span class="nt">></span>p:OnEventCorrelation<span class="nt"></ns:processType></span>
+ ... exchanges
+ <span class="nt"></ns:restoreInstance></span>
+ <span class="nt"></replay></span>
+ <span class="nt"></pmap:replay></span>
+</pre></div>
+
+
+<p><a name="InstanceReplayer-TimecontrolinBPEL"></a></p>
+<h2 id="time-control-in-bpel">Time control in BPEL</h2>
+<p>To have control over time in bpel process, there is a new variable introduced, $ode:currentEventDateTime.
+It's equivalent to $fn:current-dateTime() during live session and it's set to corresponding time in past during replaying.</p>
+<p><a name="InstanceReplayer-Implementationnotes"></a></p>
+<h2 id="implementation-notes">Implementation notes</h2>
+<ul>
+<li>Replaying works in one transaction.
+You can migrate a few instances at once and get an error, which will roll back all work if an error occurrs in some case.</li>
+<li>Replayer extends BpelRuntimeContextImpl by ReplayerBpelRuntimeContextImpl class, which overrides methods like invoke and registerTimer to mock up communication.</li>
+<li>It implements ReplayerScheduler, which executes actions from past in time sorted order (exchanges given to replayer have createTime field, which is used for sorting)</li>
+<li>jobs from past are processed in ReplayerScheduler and jobs in future are registered in engine's scheduler</li>
+<li>In order to make integrity constraints, replaying returns error if:
+<strong> a first incoming request is routed to an existing instance instead of creating a new one
+</strong> next incoming request is routed to other instance or creates a new instance
+** there is some unprocessed communication while finishing replaying (for example if there is some outgoing exchange for service, which did not have INVOKE from replayed instance)</li>
+<li>It extends bpel-compiler and xpath evaluation by $ode:currentEventDateTime variable</li>
+<li>It adds currentEventDateTime property to BpelRuntimeContext</li>
+<li>It adds replayer package to bpel engine in bpel-runtime module</li>
+<li>It changes visibility of some fields and methods in bpel engine from private to protected and from optional to public.</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/userguide/jbi-deployment.html
==============================================================================
--- websites/staging/ode/trunk/content/userguide/jbi-deployment.html (original)
+++ websites/staging/ode/trunk/content/userguide/jbi-deployment.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/management-api.html
==============================================================================
--- websites/staging/ode/trunk/content/userguide/management-api.html (added)
+++ websites/staging/ode/trunk/content/userguide/management-api.html Fri Dec 28 13:13:46 2012
@@ -0,0 +1,138 @@
+<!DOCTYPE html>
+<html>
+ <head>
+ <title>Management API</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>Management API</h1>
+
+ </div>
+ </header>
+
+
+ <!-- Content -->
+ <div class="container">
+
+ <div class="row">
+ <div class="span12">
+ <h2 id="overview">Overview</h2>
+<p>ODE has a complete management API to check which processes are deployed, running and completed instances, variables values and more. To see which methods are available, have a look at the <a href="http://ode.apache.org/javadoc/org/apache/ode/bpel/pmapi/ProcessManagement.html">ProcessManagement</a> and <a href="http://ode.apache.org/javadoc/org/apache/ode/bpel/pmapi/InstanceManagement.html">InstanceManagement</a> interfaces, the javadoc is pretty comprehensive.</p>
+<p>These two interfaces are available as web services on the Axis2-based distribution. The corresponding WSDL can be found <a href="http://svn.apache.org/repos/asf/ode/trunk/axis2/src/main/wsdl/pmapi.wsdl">here</a>.</p>
+<p>To invoke these two services, any web service client should work (in a perfect interoperable world). To ease the invocation when using an Axis2 client, a helper class is bundled in ode-axis2.jar: <a href="http://ode.apache.org/javadoc/axis2/org/apache/ode/axis2/service/ServiceClientUtil.html">ServiceClientUtil</a>. Usage examples are also available in test classes <a href="http://svn.apache.org/repos/asf/ode/trunk/axis2/src/test/java/org/apache/ode/axis2/management/InstanceManagementTest.java">InstanceManagementTest</a> and <a href="http://svn.apache.org/repos/asf/ode/trunk/axis2/src/test/java/org/apache/ode/axis2/management/ProcessManagementTest.java">ProcessManagementTest</a>. Here is a short example demonstrating the invocation of the <em>listAllProcesses</em> operation:
+ :::java
+ ServiceClientUtil client = new ServiceClientUtil();
+ OMElement root = client.buildMessage("listAllProcesses", new String<a href=".html"></a> {}, new String[] {});
+ OMElement result = client.send(msg, "http://localhost:8080/ode/processes/ProcessManagement");</p>
+<p>We're using <a href="http://xmlbeans.apache.org/">XMLBeans</a> to serialize and deserialize the returned values from/to XML so in the previous example. So if you'd like to have objects instead of an <a href="http://ws.apache.org/commons/axiom/index.html">Axiom</a> structure in the previous example, just add the following lines of code:</p>
+<div class="codehilite"><pre><span class="n">ScopeInfoDocument</span> <span class="n">scopeIndoDoc</span> <span class="o">=</span> <span class="n">ScopeInfoDocument</span><span class="o">.</span><span class="na">Factory</span><span class="o">.</span><span class="na">parse</span><span class="o">(</span><span class="n">result</span><span class="o">.</span><span class="na">getXMLStreamReader</span><span class="o">());</span>
+</pre></div>
+
+
+<p>You will need to include ode-bpel-api.jar in your classpath.</p>
+<p><a name="ManagementAPI-Specification"></a></p>
+<h2 id="specification">Specification</h2>
+<p>More details are available in the <a href="bpel-management-api-specification.html">Process Management API specification</a></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/ode-execution-events.html
==============================================================================
--- websites/staging/ode/trunk/content/userguide/ode-execution-events.html (added)
+++ websites/staging/ode/trunk/content/userguide/ode-execution-events.html Fri Dec 28 13:13:46 2012
@@ -0,0 +1,223 @@
+<!DOCTYPE html>
+<html>
+ <head>
+ <title>ODE Execution Events</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>ODE Execution Events</h1>
+
+ </div>
+ </header>
+
+
+ <!-- Content -->
+ <div class="container">
+
+ <div class="row">
+ <div class="span12">
+ <p>ODE generates events to let you track what is exactly happening in the engine and produces detailed information about process executions. These events are persisted in ODE's database and can be queried using the <a href="management-api.html">Management API</a>. The default behavior for the engine is to always generate all events for every executed action. However from a performance standpoint it's a good idea to deactivate some of the events you're not interested in (or even all of them). Inserting all these events generates a non-negligeable overhead.</p>
+<p><a name="ODEExecutionEvents-Eventtypes"></a></p>
+<h3 id="event-types">Event types</h3>
+<p>The following table details each event possibly generated by ODE:</p>
+<table>
+<tr><th>Event Name</th><th>Process/Scope</th><th>Description</th><th>Type</th></tr>
+<tr><td>ActivityEnabledEvent </td><td> Scope </td><td> An activity is enabled (just before it's started) </td><td> activityLifecycle
+</tr>
+<tr><td>ActivityDisabledEvent </td><td> Scope </td><td> An activity is disabled (due to dead path elimination) </td><td> activityLifecycle
+</tr>
+<tr><td>ActivityExecStartEvent </td><td> Scope </td><td> An activity starts its execution </td><td> activityLifecycle
+</tr>
+<tr><td>ActivityExecEndEvent </td><td> Scope </td><td> An activity execution terminates </td><td> activityLifecycle
+</tr>
+<tr><td>ActivityFailureEvent </td><td> Scope </td><td> An activity failed </td><td> activityLifecycle
+</tr>
+<tr><td>CompensationHandlerRegistered </td><td> Scope </td><td> A compensation handler gets registered on a scope </td><td> scopeHandling
+</tr>
+<tr><td>CorrelationMatchEvent </td><td> Process </td><td> A matching correlation has been found upon reception of a message </td><td> correlation
+</tr>
+<tr><td>CorrelationNoMatchEvent </td><td> Process </td><td> No matching correlation has been found upon reception of a message </td><td> correlation
+</tr>
+<tr><td>CorrelationSetWriteEvent </td><td> Scope </td><td> A correlation set value has been initialized </td><td> dataHandling
+</tr>
+<tr><td>ExpressionEvaluationFailedEvent </td><td> Scope </td><td> The evaluation of an expression failed </td><td> dataHandling
+</tr>
+<tr><td>ExpressionEvaluationSuccessEvent </td><td> Scope </td><td> The evaluation of an expression succeeded </td><td> dataHandling
+</tr>
+<tr><td>NewProcessInstanceEvent </td><td> Process </td><td> A new process instance is created </td><td> instanceLifecycle
+</tr>
+<tr><td>PartnerLinkModificationEvent </td><td> Scope </td><td> A partner link has been modified (a new value has been assigned to it) </td><td> dataHandling
+</tr>
+<tr><td>ProcessCompletionEvent </td><td> Process </td><td> A process instance completes </td><td> instanceLifecycle
+</tr>
+<tr><td>ProcessInstanceStartedEvent </td><td> Process </td><td> A process instance starts </td><td> instanceLifecycle
+</tr>
+<tr><td>ProcessInstanceStateChangeEvent </td><td> Process </td><td> The state of a process instance has changed </td><td> instanceLifecycle
+</tr>
+<tr><td>ProcessMessageExchangeEvent </td><td> Process </td><td> A process instance has received a message </td><td> instanceLifecycle
+</tr>
+<tr><td>ProcessTerminationEvent </td><td> Process </td><td> A process instance terminates </td><td> instanceLifecycle
+</tr>
+<tr><td>ScopeCompletionEvent </td><td> Scope </td><td> A scope completes </td><td> scopeHandling
+</tr>
+<tr><td>ScopeFaultEvent </td><td> Scope </td><td> A fault has been produced in a scope </td><td> scopeHandling
+</tr>
+<tr><td>ScopeStartEvent </td><td> Scope </td><td> A scope started </td><td> scopeHandling
+</tr>
+<tr><td>VariableModificationEvent </td><td> Scope </td><td> The value of a variable has been modified </td><td> dataHandling
+</tr>
+<tr><td>VariableReadEvent </td><td> Scope </td><td> The value of a variable has been read </td><td> dataHandling
+</tr>
+</table>
+
+<p>The second column specifies wether an event is associated with the process itself or with one of its scopes. The event type is used for filtering events.</p>
+<p><a name="ODEExecutionEvents-Filteringevents"></a></p>
+<h3 id="filtering-events">Filtering events</h3>
+<p><a name="ODEExecutionEvents-Filteringattheprocesslevel"></a></p>
+<h4 id="filtering-at-the-process-level">Filtering at the process level</h4>
+<p>Using ODE's deployment descriptor, it's possible to tweak events generation to filtrate which ones get created. First, events can be filtered at the process level using one of the following stanza:</p>
+<div class="codehilite"><pre><span class="nt"><dd:process-events</span> <span class="na">generate=</span><span class="s">"all"</span><span class="nt">/></span> <span class="c"><!-- Default configuration --></span>
+
+<span class="nt"><dd:process-events</span> <span class="na">generate=</span><span class="s">"none"</span><span class="nt">/></span>
+
+<span class="nt"><dd:process-events></span>
+ <span class="nt"><dd:enable-event></span>dataHandling<span class="nt"></dd:enable-event></span>
+ <span class="nt"><dd:enable-event></span>activityLifecycle<span class="nt"></dd:enable-event></span>
+<span class="nt"></dd:process-events></span>
+</pre></div>
+
+
+<p>The first form just duplicates the default behaviour, when nothing is specified in the deployment descriptor, all events are generated. The third form lets you define which type of event is generated, possible types are: <code>instanceLifecycle</code>, <code>activityLifecycle</code>, <code>dataHandling</code>, <code>scopeHandling</code>, <code>correlation</code>.</p>
+<p><a name="ODEExecutionEvents-Filteringatthescopelevel"></a></p>
+<h4 id="filtering-at-the-scope-level">Filtering at the scope level</h4>
+<p>It's also possible to define filtering for each scope of your process. This overrides the settings defined on the process. In order to define event filtering on a scope, the scope activity MUST have a name in your process definition. Scopes are referenced by name in the deployment descriptor:</p>
+<div class="codehilite"><pre><span class="nt"><dd:deploy</span> <span class="na">xmlns:dd=</span><span class="s">"http://www.apache.org/ode/schemas/dd/2007/03"</span><span class="nt">></span>
+ ...
+ <span class="nt"><dd:process-events</span> <span class="na">generate=</span><span class="s">"none"</span><span class="nt">></span>
+ <span class="nt"><dd:scope-events</span> <span class="na">name=</span><span class="s">"aScope"</span><span class="nt">></span>
+ <span class="nt"><dd:enable-event></span>dataHandling<span class="nt"></bpel:enable-event></span>
+ <span class="nt"><dd:enable-event></span>scopeHandling<span class="nt"></bpel:enable-event></span>
+ <span class="nt"></dd:scope-events></span>
+ <span class="nt"><dd:scope-events</span> <span class="na">name=</span><span class="s">"anotherScope"</span><span class="nt">></span>
+ <span class="nt"><dd:enable-event></span>activityLifecycle<span class="nt"></bpel:enable-event></span>
+ <span class="nt"></dd:scope-events></span>
+ <span class="nt"></dd:process-events></span>
+ ...
+<span class="nt"></dd:deploy></span>
+</pre></div>
+
+
+<p>Note that it's useless to enable an event associated with the process itself when filtering events on scopes.</p>
+<p>The filter defined on a scope is automatically inherited by its inner scopes. So if no filter is defined on a scope, it will use the settings of its closest parent scope having event filters (up to the process). Note that what gets inherited is the full list of selected events, not each event definition individually.</p>
+<p><a name="ODEExecutionEvents-Eventlisteners"></a></p>
+<h3 id="event-listeners">Event listeners</h3>
+<p>ODE lets you register your own event listeners to analyze all produced events and do whatever you want to do with them. To create a listener you just need to implement the <a href="https://svn.apache.org/repos/asf/ode/trunk/bpel-api/src/main/java/org/apache/ode/bpel/iapi/BpelEventListener.java">org.apache.ode.bpel.iapi.BpelEventListener</a> interface.</p>
+<p>Then add your implementation in the server's classpath and add a property in ode-axis2.properties giving your fully qualified implementation class name. Something like:</p>
+<div class="codehilite"><pre><span class="n">ode</span><span class="o">-</span><span class="n">axis2</span><span class="o">.</span><span class="n">event</span><span class="o">.</span><span class="n">listeners</span><span class="o">=</span><span class="n">com</span><span class="o">.</span><span class="n">compamy</span><span class="o">.</span><span class="n">product</span><span class="o">.</span><span class="n">MyOdeEventListener</span>
+</pre></div>
+
+
+<p>Start your server and you're done!</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/process-versioning.html
==============================================================================
--- websites/staging/ode/trunk/content/userguide/process-versioning.html (added)
+++ websites/staging/ode/trunk/content/userguide/process-versioning.html Fri Dec 28 13:13:46 2012
@@ -0,0 +1,164 @@
+<!DOCTYPE html>
+<html>
+ <head>
+ <title>Process Versioning * [Introduction](#ProcessVersioning-Introduction) * [How Versioning Works](#ProcessVersioning-HowVersioningWorks) * [Process Versioning in ODE](#ProcessVersioning-ProcessVersioninginOde) * [Remote Deployment vs. Hand-Made Deployment](#ProcessVersioning-RemoteDeploymentvs.Hand-MadeDeployment)</title>
+ <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>Process Versioning * [Introduction](#ProcessVersioning-Introduction) * [How Versioning Works](#ProcessVersioning-HowVersioningWorks) * [Process Versioning in ODE](#ProcessVersioning-ProcessVersioninginOde) * [Remote Deployment vs. Hand-Made Deployment](#ProcessVersioning-RemoteDeploymentvs.Hand-MadeDeployment)</h1>
+
+ </div>
+ </header>
+
+
+ <!-- Content -->
+ <div class="container">
+
+ <div class="row">
+ <div class="span12">
+ <p><a name="ProcessVersioning-Introduction"></a></p>
+<h3 id="introduction">Introduction</h3>
+<p>Before starting on what process versioning exactly does, let's see what the world (or at least ODE) would be without versioning. It will be much more easier for you to understand the solution after fully seeing the problem.</p>
+<p>So you're starting using ODE and you've just designed you first business process. It's all nice and dandy and works perfectly. It works so well that you let your users start using it. It's not really production but you know, release early, release often, so let's see what users think of it. After a couple of days you realize that a couple of steps are missing, you add them in your process and once again, it executes smoothly. So let's see what our users think of the improvement! Next thing you know, your phone starts ringing and the user on the other side is most likely pretty upset. What happened?</p>
+<p>So when you start using a process, executions for it are created, running processes if you like (also called process instances). Depending on the type of your business these could take a variable amount of time to execute but they're usually not instantaneous. So you have all these running processes sometimes doing things, sometimes just waiting there and all of a sudden, a brand new process definition replaces the original one all these executions have been using so far. What is a process engine to do with all these executions? Well, the most logic thing on earth: just nuke them all.</p>
+<p>At this time there's no simple automated way to migrate a running process that has been executing using one definition to another new one. Computing the differences between the 2 definitions can be very complex and chances are that they're not even compatible! When you think of all these little tasks that are arranged just so to guarantee a perfect execution using the right data types, even minor alterations can get really tricky to apply on instances without blowing them all.</p>
+<p>So here is the crude and sad truth: without having some versioning goodness in it, a process engine will always delete all the running instances when a new process definition is deployed.</p>
+<p><a name="ProcessVersioning-HowVersioningWorks"></a></p>
+<h3 id="how-versioning-works">How Versioning Works</h3>
+<p>So if existing executions can't be migrated, what are you going to do with them? Well, just let them be. Versioning is based on the fact that, instead of directly updating the original process definition (leaving its instances to their dreadful fate), another new version of this definition is created. The older one is declared retired so no new executions can be started on that one, the new process is the one to be used now on. But running instances can still finish their job peacefully as the process they've been using to execute so far is still available and unchanged.</p>
+<p>However ODE also has the concept of deployment bundles and supports 2 modes of deployment (remotely or manually directly on the filsesystem). Let's see how we get versioning to work under those conditions.</p>
+<p><a name="ProcessVersioning-ProcessVersioninginOde"></a></p>
+<h4 id="process-versioning-in-ode">Process Versioning in ODE</h4>
+<p>In ODE, processes are deployed in what we call a deployment bundle. When you come down to it, it's just a zip file or a directory containing ODE's deployment descriptor (<a href="creating-a-process#deployment-descriptor.html">deploy.xml</a>), the processes BPEL and all the other goodies necessary for your BPEL to run (WSDLs, schemas, xsl stylesheets, you name it). And what ODE is using to know you're redeploying the same thing is the deployment bundle name.</p>
+<p>So when you're redeploying a deployment bundle in ODE, here is what happens:</p>
+<ol>
+<li>A new version is attributed to the bundle by incrementing the version number of the last deployment.</li>
+<li>ODE checks whether the same bundle has been deployed before, <em>all</em> processes in those older bundles are retired.</li>
+<li>The processes in the bundle are deployed in the engine using the same version number as the bundle itself.</li>
+<li>New executions of all newly deployed processes are ready to be started.</li>
+</ol>
+<p>There are a couple of additional remarks to make. The first is that the version is a single, sequentially incremented (which is to say that 3 comes after 2 and 2 comes after 1) number. <em>All</em> deployed bundles share the same sequence. The second thing to be aware of is that all processes in a bundle share the same version number and it's the number of their bundle.</p>
+<p>Let's use the notation Foo-x(Bar-x, Baz-x) to represent the deployment of the Foo bundle in version x with processes Bar and Baz (sharing the same version number as just explained). The following illustrates a valid deployment sequence:</p>
+<ol>
+<li>Coconut-1(Pineapple-1, Mango-1)</li>
+<li>Orange-2(Tangerine-2)</li>
+<li>Orange-3(Tangerine-3) => retires Orange-2(Tangerine-2)</li>
+<li>Coconut-4(Pineapple-4, Mango-4) => retires Coconut-1(Pineapple-1, Mango-1)</li>
+<li>Banana-5(Kiwi-5)</li>
+</ol>
+<p>That's both tasty and healthy! </p>
+<p>There's still a last question left unsolved: what happens if you take your bundle and deploy it under a different name with the same content. If you know a bit about source version control (like CVS or Subversion), that's very close to branching, only you might be executing two branches at the same time. As ODE can't find another bundle with the same, the processes will simply be deployed <em>without</em> retiring anything. You will effectively have twice the same process deployed under different versions. In that scenario you're supposed to know what you're doing. </p>
+<p>If two identical process definitions are deployed at the same time, the behavior of the engine is unspecified. Which one of the two process will pick up the message? Who knows!? But this can be a very useful feature in specific cases when you want to deploy the same process twice (by same understand same name and same namespace) but the 2 definitions are actually different and enable different endpoints. This allows the parallel deployment of two different version of the same process provided that they don't overlap in their endpoint implementation.</p>
+<p><a name="ProcessVersioning-RemoteDeploymentvs.Hand-MadeDeployment"></a></p>
+<h4 id="remote-deployment-vs-hand-made-deployment">Remote Deployment vs. Hand-Made Deployment</h4>
+<p>ODE supports 2 different ways of deploying bundles:</p>
+<ul>
+<li>using the deployment web service or JBI deployment.</li>
+<li>dropping bundles as directories under WEB-INF/processes.</li>
+</ul>
+<p>The first way works just as described previously. Under the hood, your process bundle is a zip and it gets unzipped in a directory named bundlename-version. The version number is automatically generated by the engine. So you only need to provide the zip itself and a consistent bundle name.</p>
+<p>For the second way, it's a bit more tricky. Because you're directly interacting with the deployment directory, you're allowed to create a bundle directory with any name you like (even not numbered at all). In that case ODE will still create a version number, it just won't be shown on the filesystem. However as it won't be able to find the previous bundle to retire, it will just deploy the new bundle along with all other processes, even if you already had some conflicting deployments. Basically, if you don't number your directories properly, every new deployment will be a new branch. In short, you don't really want to do that.</p>
+<p>Another thing you're allowed to do with the file system is simply to replace (or remove and copy) all the files in the deployment bundle directory and remove the .deployed marker file to trigger redeployment. In that case ODE will simply consider you've undeployed and deployed the whole thing. So we get back to the situation where we don't have any versioning. Which can be very useful when you're in development mode because you usually don't care much about the running instances and you usually don't want to pile up versions of process definitions.</p>
+ </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/smx4-osgi-deployment.html
==============================================================================
--- websites/staging/ode/trunk/content/userguide/smx4-osgi-deployment.html (original)
+++ websites/staging/ode/trunk/content/userguide/smx4-osgi-deployment.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/userguide/upgrading-ode.html
==============================================================================
--- websites/staging/ode/trunk/content/userguide/upgrading-ode.html (original)
+++ websites/staging/ode/trunk/content/userguide/upgrading-ode.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/userguide/war-deployment.html
==============================================================================
--- websites/staging/ode/trunk/content/userguide/war-deployment.html (original)
+++ websites/staging/ode/trunk/content/userguide/war-deployment.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/wsdl-11-http-binding-support.html
==============================================================================
--- websites/staging/ode/trunk/content/userguide/wsdl-11-http-binding-support.html (added)
+++ websites/staging/ode/trunk/content/userguide/wsdl-11-http-binding-support.html Fri Dec 28 13:13:46 2012
@@ -0,0 +1,128 @@
+<!DOCTYPE html>
+<html>
+ <head>
+ <title>WSDL 1.1 HTTP Binding Support</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>WSDL 1.1 HTTP Binding Support</h1>
+
+ </div>
+ </header>
+
+
+ <!-- Content -->
+ <div class="container">
+
+ <div class="row">
+ <div class="span12">
+ <p>Since version <a href="getting-ode.html">1.2</a>, ODE supports <a href="http://www.w3.org/TR/wsdl#_http">HTTP Binding</a>. ODE is almost fully compliant with the WSDL 1.1 spec. The few limitations are related to MIME types.
+Actually only the following <a href="http://www.iana.org/assignments/media-types/">MIME types</a> are supported:
+1. Media types that represent <a href="http://www.rfc-editor.org/rfc/rfc3023.txt">XML MIME entities</a>. Basically any types matching <code>"text/xml"</code>, <code>"application/xml"</code> and <code>"\*+xml"</code>.
+1. Non-XML types will be processed as Text, thus Text Media Types comes de facto but they may have a very limited set of usages.</p>
+<p><a href="http://www.w3.org/TR/wsdl#_mime:multipartRelated">mime:multipartRelated</a>, <a href="http://www.w3.org/TR/wsdl#_mime:soap:body">mime:soap:body</a> and <a href="http://www.w3.org/TR/wsdl#_mime:mimeXml">mime:mimeXml</a> are not supported.</p>
+<p>Considering how unsuitable WSDL 1.1 HTTP Binding is for a large majority of services -- especially RESTful services -- a set of extensions is available.
+All the details you want to know are <a href="wsdl-1.1-extensions-for-rest.html">here</a>.</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/using-a-jndi-datasource-under-servicemix-jbi.html
==============================================================================
--- websites/staging/ode/trunk/content/using-a-jndi-datasource-under-servicemix-jbi.html (original)
+++ websites/staging/ode/trunk/content/using-a-jndi-datasource-under-servicemix-jbi.html 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/validate.html
==============================================================================
--- websites/staging/ode/trunk/content/validate.html (original)
+++ websites/staging/ode/trunk/content/validate.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/writing-bpel-test-cases.html
==============================================================================
--- websites/staging/ode/trunk/content/writing-bpel-test-cases.html (original)
+++ websites/staging/ode/trunk/content/writing-bpel-test-cases.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>