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/11 13:48:21 UTC
svn commit: r841679 [3/3] - in /websites/staging/ode/trunk/content: ./
developerguide/ userguide/
Added: websites/staging/ode/trunk/content/developerguide/stateful-exchange-protocol.html
==============================================================================
--- websites/staging/ode/trunk/content/developerguide/stateful-exchange-protocol.html (added)
+++ websites/staging/ode/trunk/content/developerguide/stateful-exchange-protocol.html Tue Dec 11 12:48:20 2012
@@ -0,0 +1,184 @@
+<!DOCTYPE html>
+<html>
+ <head>
+ <title>Stateful Exchange Protocol</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="active 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="/user-guide.html">User Guide</a></li>
+ <li><a href="/developer-guide.html">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="/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>Stateful Exchange Protocol</h1>
+
+ </div>
+ </header>
+
+
+ <!-- Content -->
+ <div class="container">
+
+ <div class="row">
+ <div class="span12">
+ <p><a name="StatefulExchangeProtocol-1.General"></a></p>
+<h2 id="1-general">1. General</h2>
+<p>[TBD: Insert overview of the world before and after automagic correlation]</p>
+<p><a name="StatefulExchangeProtocol-2.StateIdentifiers"></a></p>
+<h2 id="2-state-identifiers">2. State Identifiers</h2>
+<p>A common use case consists of a client that needs to invoke multiple operations against the same service. Each operation depends on the state resulting from the completion of the previous operation. The service needs to associate these invocations with states it maintains internally. That's the basis for the State Exchange protocol.</p>
+<p>In the initial invocation, the client sends a request to the service. The service returns a response that includes a <em>state identifier</em>. The state identifier is opaque to the client, however, the client knows to use that state identifier in subsequent invocations that depend on the state of the pervious invocation.</p>
+<p>In a subsequent invocation, the client sends a request to the service and includes the state identifier. The service is able to associate this request with thwe state reached by the previous request.</p>
+<p>The exact mechanism for carrying the state identifier depends on the underlying transport protocol and the message wire format. This specification provides bindings for SOAP and HTTP.</p>
+<p>The protocol requires an initial two-way operation, followed by any combination of two-way and one-way operations.</p>
+<p>The service can decide how long to keep an association between the state identifier and any internal state, and how to deal with failure conditions that may result in loss of state. A service should express its ability to maintain state association through its policy.</p>
+<p>The service responds with an error if it expects to receive a state identifier and does not find one in the message, or if it cannot associate the state identifier with any known state.</p>
+<p>Unless specified otherwise, the client expects to receive the same state identifier in subsequent invocations of the service. The client may detect an error condition if it sends one state identifier and receives another. Unless specified otherwise, the client may conclude that the state identifier is no longer associated with any state if it receives a response that does not include a state identifier.</p>
+<p>Although the state identifier is opaque to the client, the client can compare state identifiers for equivalence. Two state identifiers are equivalent if they contain the same set of characters.</p>
+<p>Services are encouraged to create unique identifiers for each internal state using globally unique identifiers. In doing so, they prevent accidental association of two unrelated states.</p>
+<p><a name="StatefulExchangeProtocol-3.StatefulEPRs"></a></p>
+<h2 id="3-stateful-eprs">3. Stateful EPRs</h2>
+<p>Some interactions involve more than one client or more than one service. These interactions require the clients and services to communicate stateful EPRs.</p>
+<p>A <em>stateful EPR</em> is an EPR that contains all the information necessary to invoke a service in association with a particular state. A stateful EPR is essentially an EPR that incorporates a state identifier. For example, when using WS-Addressing, the stateful EPR will include the state identifier as a reference property.</p>
+<p>The client obtains the stateful EPR in one of three ways:
+<em> By composition.
+</em> From a header or the body of the message.
+* From the state callback header.</p>
+<p>When using WS-Addressing, the client can compose the stateful EPR by combining the service EPR and the state identifier, using the state identifier as a reference property.</p>
+<p>All addressing mechanisms support stateful EPRs. However, not all addressing mechanisms allow the client to compose stateful EPRs. For example, when using the HTTP protocol bindings, only the service can construct stateful EPRs.</p>
+<p>The service may also send a stateful EPR in a header or the body of the message. The service may send its own stateful EPR, or the stateful EPR of a different service (see <em>Shared States</em>). The state callback header is a special case of that (see <em>State Callback</em>).</p>
+<p><a name="StatefulExchangeProtocol-4.SharedStates"></a></p>
+<h2 id="4-shared-states">4. Shared States</h2>
+<p>There are cases where two or more services share a common state. This non-normative part of the specification provides guidelines for implementing such scenarios.</p>
+<p>For example, a process may implement two services that both affect the same process instance (internal state). The client invokes operations on the first service against the same process instance by using one state identifier. The client then needs to invoke operations on the second service against the same process instanace.</p>
+<p>The two services use different EPRs, and the client may not be able to deduct one stateful EPR from the other. In fact, it is highly recommended that the two stateful EPRs use different state identifiers. Instead, the first service obtains the stateful EPR of the second service and sends it to the client.</p>
+<p>In this case, the first service obtains the stateful EPR of the second service and sends it to the client.</p>
+<p>For example, a BPEL process may receive a request on one partnerLink, assign the myRole EPR of another partnerLink to a message and reply with that message. After extracting the EPR from the message, the client is able to invoke the same process instance using the second partnerLink.</p>
+<p>To support this pattern we recommend that a BPEL implementation construct a stateful EPR for a partnerLink myRole on or before first use. First use occurs when that partnerLink myRole is assigned to a variable, or communicated in the header of a message by a process instance. Once set, the stateful EPR remains the same until discarded by the process instance.</p>
+<p><a name="StatefulExchangeProtocol-5.StateCallback"></a></p>
+<h2 id="5-state-callback">5. State Callback</h2>
+<p>There are may ways in which services can be combined using stateful message exchanges. A common pattern consists of a two-way exchange between two services acting as peers invoke each other. This pattern is common enough that the State Exchange protocol introduces a specific header to cater for it.</p>
+<p>The State Exchange protocol supports this pattern using <em>state callback headers</em>. State callback headers are sent in addition to state identifiers to provide a callback address. They are used to associate two states with each other.</p>
+<p>In the initial invocation, the first service constructs a stateful EPR and sends it as a state callback header. The second service returns a response with a state identifier. In a subsequent invocation, the first service uses that state identifier to invoke the second service.</p>
+<p>The second service may also follow up with an invocation of the first service using the stateful EPR provided in the state callback header. In this manner, both services can invoke each other within the same interaction.</p>
+<p>Both services maintain their own internal states and use separate state identifiers. The state association results from invocations that, regardless of direction, refer to both internal states.</p>
+<p>In order to support addressing schemes that do not allow the client to compose a stateful EPR, a service may return a callback state header in lieu of, or in addition to the state identifier. The client may then choose whether to use the state identifier or stateful EPR for subsequent invocations of that service.</p>
+<p><a name="StatefulExchangeProtocol-6.Fail-fastMechanism"></a></p>
+<h2 id="6-fail-fast-mechanism">6. Fail-fast Mechanism</h2>
+<p>TBD: Cleanup</p>
+<p>An important characteristic of the State Exchange protocol is that clients and servers must be aware whether the interaction is in fact stateful. Reaching that decision is not always possible, but for the benefit of protocols that allow it, we introduce a fail-fast mechanism.</p>
+<p>When the client sends a message to the service that does not require the state identifier or state callback header, it may use the <em>state use</em> header instead. This header informs the service that the client supports state exchange. The client may also force the service to process the header (e.g. using the SOAP <em>mustUnderstand</em> attribute) to guarantee that the service supports state exchange.</p>
+<p><a name="StatefulExchangeProtocol-7.SOAPBindings"></a></p>
+<h2 id="7-soap-bindings">7. SOAP Bindings</h2>
+<p>When using SOAP, the state identifier is sent in the header <code>state:identifier</code> and the callback EPR is sent in the header <code>state:callback</code>. If the message does not contain either header, it may use the <code>state:use</code> header to indicate support for the State Exchange protocol.</p>
+<p>The <code>state:identifier</code> header is an element of type xsd:string that contains an opaque identifier.</p>
+<p>The <code>state:callback</code> header is an element of type <code>wsa:EndpointReference</code> that contains a WS-Addressing EPR. It must contain the reference property state:identifier.</p>
+<p>The <code>state:use</code> header is an element of type <code>xsd:boolean</code> that must contain the value true.</p>
+<p>The <code>state:identifier</code> header must be present in any response message, as long as the service can maintain an association for that state identifier. A response message that does not include the state:identifier header signals to the client that the service no longer accepts that state identifier.</p>
+<p>A client can compose the stateful EPR of a service by combining the service EPR with the <code>state:identifier</code> header, using it as a reference property. When it sends a message to the service, it uses the service EPR and copies the state:identifier element to the header of the SOAP message. In doing so, it fulfills the requirements of both WS-Addressing and State Exchange protocol.</p>
+<p>To fail fast is the protocol is not supported, clients are encouraged to use the mustUnderstand attribute to force the service to process state headers. Services are encourage to look for the existence of a state header to determine if the client supports the State Exchange protocol. Additional checking can be done on response messages.</p>
+<p>The following table summarizes SOAP faults used by the State Exchange protocol:
+<table class="table table-bordered">
+ <tbody>
+ <tr><td><code>state:missingIdentifier</code></td><td>The service expects to receive a state identifier and did not find one in the message.</td></tr>
+ <tr><td><code>state:noSuchState</code></td><td>The state identifier is not associated with any internal state maintained by the service.</td></tr>
+ <tr><td><code>state:missingHeader</code></td><td>The service expects a state exchange and the client did not provide any state header.</td></tr>
+ <tr><td><code>state:invalidCallback</code></td><td>The <code>state:callback</code> header cannot be used as an endpoint reference.</td></tr>
+ </tbody>
+</table></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/sitemap.html
==============================================================================
--- websites/staging/ode/trunk/content/sitemap.html (original)
+++ websites/staging/ode/trunk/content/sitemap.html Tue Dec 11 12:48:20 2012
@@ -88,9 +88,7 @@
<li><a href="/agha86.html">Agha86</a></li>
<li><a href="/ambiguousreceive.html">ambiguousReceive</a></li>
<li><a href="/ant-tasks.html">Ant Tasks</a></li>
-<li><a href="/architectural-overview.html">Architectural Overview</a></li>
<li><a href="/assign.html">assign</a></li>
-<li><a href="/atomic-scopes-extension-for-bpel.html">Atomic Scopes Extension for BPEL</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>
@@ -107,9 +105,7 @@
<li><a href="/ddvalidate-command.html">ddvalidate Command</a></li>
<li><a href="/deployment-unit.html">deployment unit</a></li>
<li><a href="/deployxml.html">deploy.xml</a></li>
-<li><a href="/developer-guide.html">Developer Guide</a></li>
<li><a href="/direct-process-to-process-communication.html">Direct Process-to-Process Communication</a></li>
-<li><a href="/eclipse-ide.html">Eclipse IDE</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>
@@ -131,8 +127,6 @@
<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="/jacob.html">JaCOb – Virtual Processing Unit</a></li>
-<li><a href="/jbi-deployment.html">JBI Deployment</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>
@@ -151,7 +145,6 @@
<li><a href="/pxe-status-command.html">pxe-status Command</a></li>
<li><a href="/pxe-undeploy-command.html">pxe-undeploy Command</a></li>
<li><a href="/receive.html">receive</a></li>
-<li><a href="/release-guidelines.html">Release Guidelines</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>
@@ -167,24 +160,19 @@
<li><a href="/sendsoap-command.html">sendsoap Command</a></li>
<li><a href="/service-providers.html">Service Providers</a></li>
<li><a href="/service.html">service</a></li>
-<li><a href="/smx4-osgi-deployment.html">SMX4 OSGi Deployment</a></li>
<li><a href="/soap-11.html">SOAP 1.1</a></li>
<li><a href="/source-code.html">Source Code</a></li>
<li><a href="/specifications-and-standards.html">Specifications and Standards</a></li>
<li><a href="/standard-faults.html">Standard Faults</a></li>
-<li><a href="/stateful-exchange-protocol.html">Stateful Exchange Protocol</a></li>
<li><a href="/system-lifecycle.html">System Lifecycle</a></li>
<li><a href="/uninitializedvariable.html">uninitializedVariable</a></li>
-<li><a href="/upgrading-ode.html">Upgrading ODE</a></li>
<li><a href="/uri.html">URI</a></li>
<li><a href="/url.html">URL</a></li>
<li><a href="/urlalias-command.html">urlalias Command</a></li>
<li><a href="/use-assign-to-build-messages.html">Use Assign to build messages</a></li>
-<li><a href="/user-guide.html">User Guide</a></li>
<li><a href="/using-a-jndi-datasource-under-servicemix-jbi.html">Using a JNDI datasource under ServiceMix JBI</a></li>
<li><a href="/validate.html">validate</a></li>
<li><a href="/version-command.html">version Command</a></li>
-<li><a href="/war-deployment.html">WAR Deployment</a></li>
<li><a href="/writing-bpel-test-cases.html">Writing BPEL Test Cases</a></li>
<li><a href="/ws-bpel-20-specification-compliance.html">WS-BPEL 2.0 Specification Compliance</a></li>
<li><a href="/ws-bpel-20.html">WS-BPEL 2.0</a></li>
Added: websites/staging/ode/trunk/content/userguide/index.html
==============================================================================
--- websites/staging/ode/trunk/content/userguide/index.html (added)
+++ websites/staging/ode/trunk/content/userguide/index.html Tue Dec 11 12:48:20 2012
@@ -0,0 +1,168 @@
+<!DOCTYPE html>
+<html>
+ <head>
+ <title>User Guide</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="/user-guide.html">User Guide</a></li>
+ <li><a href="/developer-guide.html">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="/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>User Guide</h1>
+
+ </div>
+ </header>
+
+
+ <!-- Content -->
+ <div class="container">
+
+ <div class="row">
+ <div class="span12">
+ <p><a name="UserGuide-GettingStarted"></a></p>
+<h2 id="getting-started">Getting Started</h2>
+<p>First of all, getting familiar with the <a href="../ws-bpel-20.html">WS-BPEL 2.0</a> standard is a very good idea. To use ODE, you will need to write processes using the BPEL language. There are several examples in our <a href="../getting-ode.html">distributions</a> that you can use to get started, but a decent understanding of the spec is assumed.</p>
+<p>Then, you can optionally check out <a href="../ode-schema.html">ODE Schema</a> page in order to install schema for your database. Please note that schemas from distribution sometimes contain errors, because of poor quality of ORM schema generators.</p>
+<p>ODE can be deployed in three different environments:</p>
+<ul>
+<li>As a simple Web Service in Axis 2, ODE is bundled in a WAR than can be deployed in any application server and is invoked using plain SOAP/HTTP.</li>
+<li>As a JBI service assembly, ODE is bundled in a ZIP that can be deployed in any JBI container and is invoked using the NMR.</li>
+<li>SMX4 OSGi bundle</li>
+</ul>
+<p><a name="UserGuide-Installation"></a></p>
+<h2 id="installation">Installation</h2>
+<ol>
+<li><a href="war-deployment.html">WAR Deployment</a></li>
+<li><a href="jbi-deployment.html">JBI Deployment</a></li>
+<li><a href="smx4-osgi-deployment.html">SMX4 OSGi Deployment</a></li>
+<li><a href="upgrading-ode.html">Upgrading ODE</a></li>
+</ol>
+<p><a name="UserGuide-UsingOde"></a></p>
+<h2 id="using-ode">Using ODE</h2>
+<ol>
+<li><a href="creating-a-process.html">Creating a Process</a></li>
+<li><a href="process-versioning.html">Process Versioning</a></li>
+<li><a href="management-api.html">Management API</a></li>
+<li><a href="instance-replayer.html">Instance Replayer</a></li>
+<li><a href="ode-execution-events.html">ODE Execution Events</a></li>
+<li><a href="endpoint-references.html">Endpoint References</a></li>
+<li><a href="wsdl-1.1-http-binding-support.html">WSDL 1.1 HTTP Binding Support</a></li>
+<li><a href="wsdl-1.1-extensions-for-rest.html">WSDL 1.1 Extensions for REST</a></li>
+<li><a href="bpel-extensions.html">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>
+<li><a href="activity-failure-and-recovery.html">Activity Failure and Recovery</a></li>
+<li><a href="xquery-extensions.html">XQuery Extensions</a></li>
+<li><a href="atomic-scopes-extension-for-bpel.html">Atomic Scopes Extension for BPEL</a></li>
+</ol>
+<p><a name="UserGuide-HowTo"></a></p>
+<h2 id="how-to">How To</h2>
+<ol>
+<li><a href="ode-jbi-and-axis2-properties-overview.html">ODE Jbi and Axis2 properties overview</a></li>
+<li><a href="controlling-ode's-memory-footprint.html">Controlling ODE's Memory Footprint</a></li>
+<li><a href="endpoint-configuration.html">Endpoint Configuration</a></li>
+<li><a href="http-authentication.html">HTTP Authentication</a></li>
+<li><a href="using-a-jndi-datasource-under-servicemix-jbi.html">Using a JNDI DataSource under ServiceMix JBI</a></li>
+<li><a href="writing-bpel-test-cases.html">Writing BPEL Test Cases</a></li>
+<li><a href="ws-security-in-ode.html">WS-Security in ODE</a></li>
+<li><a href="use-assign-to-build-messages.html">Use Assign to build messages</a></li>
+</ol>
+ </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/jbi-deployment.html
==============================================================================
--- websites/staging/ode/trunk/content/userguide/jbi-deployment.html (added)
+++ websites/staging/ode/trunk/content/userguide/jbi-deployment.html Tue Dec 11 12:48:20 2012
@@ -0,0 +1,223 @@
+<!DOCTYPE html>
+<html>
+ <head>
+ <title>JBI Deployment</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="/user-guide.html">User Guide</a></li>
+ <li><a href="/developer-guide.html">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="/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>JBI Deployment</h1>
+
+ </div>
+ </header>
+
+
+ <!-- Content -->
+ <div class="container">
+
+ <div class="row">
+ <div class="span12">
+ <h2 id="overview">Overview</h2>
+<p>Here's a quick overview to deploy PXE/ODE on a JBI container (e.g. <a href="http://servicemix.apache.org">ServiceMix</a>)</p>
+<p><a name="JBIDeployment-1)DownloadtheJBIdistribution"></a></p>
+<h2 id="1-download-the-jbi-distribution">1) Download the JBI distribution</h2>
+<p>Check our <a href="getting-ode.html">download page</a> and get the latest JBI-based distribution. Unzip it in a directory of your choice. We'll now refer to this directory as ODE_HOME.</p>
+<p><a name="JBIDeployment-2)InstallonJBIcontainer"></a></p>
+<h2 id="2-install-on-jbi-container">2) Install on JBI container</h2>
+<p>For example, with ServiceMix you can use file-system deployment:</p>
+<div class="codehilite"><pre>(from ode/jbi directory)
+cp ODE_HOME/ode-jbi-1.1.zip SERVICEMIX_DIR/install
+</pre></div>
+
+
+<p>The above will result in ODE being installed with the default settings. You may wish to first modify the <code>ode-jbi.properties</code> file found in the root of the installer ZIP.</p>
+<p><a name="JBIDeployment-3)DeployingProcesses"></a></p>
+<h3 id="3-deploying-processes">3) Deploying Processes</h3>
+<p>We are assuming that the reader is familiar with JBI deployment concepts. Deploying a process consists of the following steps:</p>
+<ol>
+<li>Create a temporary <em>service unit</em> directory for the BPEL processes</li>
+<li>Place the relevant <code>.bpel</code>, <code>.wsdl</code> and <code>.xsd</code> files into the temporary directory</li>
+<li>Create an ODE deployment descriptor (<code>[deploy.xml](deploy.xml.html)</code>) and place it in the temporary directory</li>
+<li>(Optional) Compile the the BPEL processes using the <code>[bpelc](bpelc.html)</code> command.</li>
+<li>Zip up the contents of the temporary directory into a service unit archive</li>
+<li>Create a temporary <em>service assembly</em> directory</li>
+<li>Place the service unit archive in a temporary <em>service assembly</em> directory</li>
+<li>Update the service assembly's <code>jbi.xml</code> descriptor</li>
+<li>Zip up the contents of the service assembly directory into a service assembly archive</li>
+<li>Copy the service assembly archive into the appropriate <em>deploy</em> directory</li>
+</ol>
+<p><a name="JBIDeployment-Examples"></a></p>
+<h2 id="examples">Examples</h2>
+<p>Some JBI examples are available under the <em>examples</em> directory of the ODE distro:</p>
+<ul>
+<li>HelloWorld2</li>
+<li>PingPong</li>
+<li>Async2</li>
+</ul>
+<p>Extract the distro-jbi-2.0-SNAPSHOT.zip created in the build instructions above.</p>
+<p>To compile the examples, you may wish to define the ODE_HOME environment variable. The build script does a good job of figuring this out without ODE_HOME set, however.</p>
+<div class="codehilite"><pre># On Linux/Unix
+export ODE_HOME=/path/to/ode/distribution
+
+# On Windows
+set ODE_HOME=C:\Path\To\ODE\Distribution
+</pre></div>
+
+
+<p>and run Ant in the example's directory:</p>
+<div class="codehilite"><pre>cd %ODE_HOME%/examples/PingPong
+ant
+</pre></div>
+
+
+<p>This will create a JBI service assembly in the "build" subdirectory. With ServiceMix you can simply copy it to the file-system hot deployment directory:</p>
+<div class="codehilite"><pre>(from PingPong directory)
+cp build/PingPing-sa.zip SERVICEMIX_DIR/deploy
+</pre></div>
+
+
+<p>Finally, you can test the example by typing:</p>
+<div class="codehilite"><pre>(from PingPong directory)
+ant test
+</pre></div>
+
+
+<p><a name="JBIDeployment-JBIEndpoints"></a></p>
+<h2 id="jbi-endpoints">JBI Endpoints</h2>
+<p>ODE now relies strictly on abstract web service definitions (i.e., without binding/service/port definitions), meaning that you only need abstract WSDLs when compiling processes. Since JBI uses normalized messages (in theory, at least), there is no need to define bindings for the BPEL service engine.</p>
+<p>In deploy.xml, you simply define the JBI internal endpoints invoked or provided by your partnerLinks,</p>
+<div class="codehilite"><pre><span class="cp"><?xml version="1.0" encoding="UTF-8"?></span>
+<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:process=</span><span class="s">"urn:/Ping.bpel"</span>
+ <span class="na">xmlns:ping=</span><span class="s">"urn:/Ping.wsdl"</span>
+ <span class="na">xmlns:pong=</span><span class="s">"urn:/Pong.wsdl"</span><span class="nt">></span>
+
+ <span class="nt"><process</span> <span class="na">name=</span><span class="s">"process:Ping"</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">"PingPartnerLink"</span><span class="nt">></span>
+ <span class="nt"><service</span> <span class="na">name=</span><span class="s">"ping:PingService"</span> <span class="na">port=</span><span class="s">"PingPort"</span><span class="nt">/></span>
+ <span class="nt"></provide></span>
+ <span class="nt"><invoke</span> <span class="na">partnerLink=</span><span class="s">"PongPartnerLink"</span><span class="nt">></span>
+ <span class="nt"><service</span> <span class="na">name=</span><span class="s">"pong:PongService"</span> <span class="na">port=</span><span class="s">"PongPort"</span><span class="nt">/></span>
+ <span class="nt"></invoke></span>
+ <span class="nt"></process></span>
+
+<span class="nt"></deploy></span>
+</pre></div>
+
+
+<p>One may use JBI binding components to make services externally available and therefore providing concrete bindings to those binding components. An example of exposing process services via SOAP/HTTP can be found in the PingPong <a href="http://svn.apache.org/repos/asf/ode/branches/APACHE_ODE_1.X/distro/src/examples-jbi/PingPong/ping-http/">ping-http service unit</a>.</p>
+<p><a name="JBIDeployment-Database"></a></p>
+<h2 id="database">Database</h2>
+<p>The generated installer will use an internally-managed embedded Derby database. No configuration is required. To use an external database one needs to modify <code>ode-jbi.properties</code> found in the component installer zip.</p>
+<p><a name="JBIDeployment-CompatibilityCaveat"></a></p>
+<h2 id="compatibility-caveat">Compatibility Caveat</h2>
+<p>Many binding components are not very good about delivering messages in the correct format for WSDL11 services.</p>
+<p><a name="JBIDeployment-KnownIssueswithServiceMix"></a></p>
+<h3 id="known-issues-with-servicemix">Known Issues with ServiceMix</h3>
+<p>ServiceMix' so-called <em>lightweight components</em> make it difficult to properly expose process services since they do not fully implement the JBI contract and do not allow the process engine to enquire about its external endpoints.
+* SoapHelper needs to properly resolve the WSDL operation name (patch available)
+<a href="https://issues.apache.org/activemq/browse/SM-488">https://issues.apache.org/activemq/browse/SM-488</a></p>
+<ul>
+<li>The servicemix-http binding component does not normalize messages</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
Added: websites/staging/ode/trunk/content/userguide/smx4-osgi-deployment.html
==============================================================================
--- websites/staging/ode/trunk/content/userguide/smx4-osgi-deployment.html (added)
+++ websites/staging/ode/trunk/content/userguide/smx4-osgi-deployment.html Tue Dec 11 12:48:20 2012
@@ -0,0 +1,194 @@
+<!DOCTYPE html>
+<html>
+ <head>
+ <title>SMX4 OSGi Deployment</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="/user-guide.html">User Guide</a></li>
+ <li><a href="/developer-guide.html">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="/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>SMX4 OSGi Deployment</h1>
+
+ </div>
+ </header>
+
+
+ <!-- Content -->
+ <div class="container">
+
+ <div class="row">
+ <div class="span12">
+ <p><a name="SMX4OSGiDeployment-DeployApacheODEOSGibundleandexampleprocess(PingPong)"></a></p>
+<h2 id="deploy-apache-ode-osgi-bundle-and-example-process-ping-pong">Deploy Apache ODE OSGi bundle and example process (Ping Pong)</h2>
+<p>Enter smx4 console and run following commands:</p>
+<div class="codehilite"><pre>features:addUrl mvn:org.apache.ode/ode-jbi-karaf/1.3.5-SNAPSHOT/xml/features
+features:install ode
+features:install examples-ode-ping-pong
+</pre></div>
+
+
+<p>This will install ODE with default settings (OpenJPA DAO, embedded Derby database)</p>
+<p><a name="SMX4OSGiDeployment-Configuringdatabase"></a></p>
+<h2 id="configuring-database">Configuring database</h2>
+<p>Create <code>SMX4/etc/org.apache.ode.jbi.cfg</code> file with following contents:</p>
+<div class="codehilite"><pre>ode-jbi.pidNamespace=urn:ode-jbi
+ode-jbi.allowIncompleteDeployment=false
+ode-jbi.messageMapper=org.apache.ode.jbi.msgmap.ServiceMixMapper
+ode-jbi.event.listeners=org.apache.ode.bpel.common.evt.DebugBpelEventListener
+
+#For MySQL
+#ode-jbi.db.int.mcf=org.tranql.connector.mysql.XAMCF
+#ode-jbi.db.int.mcf.databaseName=ODE
+#ode-jbi.db.int.mcf.userName=root
+#ode-jbi.db.int.mcf.password=root
+#ode-jbi.db.int.mcf.serverName=localhost
+
+#For Postgres
+#ode-jbi.db.int.mcf=org.tranql.connector.postgresql.PGXAMCF
+#ode-jbi.db.int.mcf.databaseName=ODE
+#ode-jbi.db.int.mcf.userName=postgres
+#ode-jbi.db.int.mcf.password=postgres
+#ode-jbi.db.int.mcf.serverName=localhost
+
+#For SQLServer
+#ode-jbi.db.int.mcf=org.tranql.connector.sqlserver.XAMCF
+#ode-jbi.db.int.mcf.databaseName=ODE
+#ode-jbi.db.int.mcf.userName=sa
+#ode-jbi.db.int.mcf.password=sa
+#ode-jbi.db.int.mcf.portNumber=1433
+#ode-jbi.db.int.mcf.serverName=localhost
+
+#For Oracle
+ode-jbi.db.int.mcf=org.tranql.connector.oracle.LocalMCF
+ode-jbi.db.int.mcf.databaseName=XE
+ode-jbi.db.int.mcf.userName=ODE
+ode-jbi.db.int.mcf.password=ode
+ode-jbi.db.int.mcf.portNumber=1521
+ode-jbi.db.int.mcf.serverName=localhost
+ode-jbi.db.int.mcf.driverType=thin
+
+# Uncomment the following to enable hibernate (this is recommended for production use):
+#ode-jbi.dao.factory=org.apache.ode.daohib.bpel.BpelDAOConnectionFactoryImpl
+</pre></div>
+
+
+<p>Please note that EXTERNAL database is currently not available in ServiceMix4, because it requires JNDI, which SMX4 doesn't support.</p>
+<p>After choosing a particular database, we need to start ODE with required dependencies. There are 2 example features prepared in ode-jbi-karaf features (ode-hib-oracle and ode-hib-sqlserver).
+So you need to run following command from Karaf console:</p>
+<div class="codehilite"><pre>features:install ode-hib-oracle
+</pre></div>
+
+
+<p>Please note that <code>etc/org.apache.ode.jbi.cfg</code> must be set to the same database (in this case oracle) to load required dependencies properly.</p>
+<p><a name="SMX4OSGiDeployment-Tips"></a></p>
+<h2 id="tips">Tips</h2>
+<p><a name="SMX4OSGiDeployment-HowtomakePMAPIwork?"></a></p>
+<h3 id="how-to-make-pmapi-work">How to make PMAPI work?</h3>
+<p>You can grab pmapi SA from here <a href="http://markmail.org/message/ghigpzcpt2j3qnoo">http://markmail.org/message/ghigpzcpt2j3qnoo</a>.
+Then edit SMX4 <code>etc/config.properties</code> and change from:</p>
+<div class="codehilite"><pre>org.osgi.framework.bootdelegation=sun.*,com.sun*,javax.transaction,javax.transaction.*
+</pre></div>
+
+
+<p>to:</p>
+<div class="codehilite"><pre>org.osgi.framework.bootdelegation=sun.*,com.sun*,javax.transaction,javax.transaction.*,javax.xml.stream,javax.xml.stream.*
+</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/upgrading-ode.html
==============================================================================
--- websites/staging/ode/trunk/content/userguide/upgrading-ode.html (added)
+++ websites/staging/ode/trunk/content/userguide/upgrading-ode.html Tue Dec 11 12:48:20 2012
@@ -0,0 +1,188 @@
+<!DOCTYPE html>
+<html>
+ <head>
+ <title>Upgrading ODE</title>
+ <meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
+ <meta property="og:image" content="http://ode.apache.org/img/ode-logo.png" />
+
+ <link href="/css/application.min.css" rel="stylesheet" media="screen">
+
+
+
+
+ </head>
+ <body>
+
+ <!-- Navbar -->
+ <div class="navbar navbar-fixed-top">
+ <div class="navbar-inner">
+ <div class="container">
+ <button type="button" class="btn btn-navbar" data-toggle="collapse" data-target=".nav-collapse">
+ <span class="icon-bar"></span>
+ <span class="icon-bar"></span>
+ <span class="icon-bar"></span>
+ </button>
+ <a class="brand" href="/index.html">Apache ODE</a>
+ <div class="nav-collapse collapse">
+ <ul class="nav">
+ <li class="">
+ <a href="/getting-ode.html">Getting ODE</a>
+ </li>
+ <li class=" dropdown">
+ <a href="/user-guide.html" class="dropdown-toggle" data-toggle="dropdown" data-target="#">Documentation<b class="caret"></b></a>
+ <ul class="dropdown-menu">
+ <li><a href="/user-guide.html">User Guide</a></li>
+ <li><a href="/developer-guide.html">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="/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>Upgrading ODE</h1>
+
+ </div>
+ </header>
+
+
+ <!-- Content -->
+ <div class="container">
+
+ <div class="row">
+ <div class="span12">
+ <div class="alert alert-note"><h4 class="alert-heading">You shall backup</h4></div>
+
+<p>ODE upgrade procedures usually consist in:</p>
+<ul>
+<li>backing up your database</li>
+<li>checking your backup</li>
+<li>double-checking your backup</li>
+<li>running the required SQL upgrade script</li>
+<li>deploying your new ODE war.</li>
+<li>copying all the previous configuration and deployed processes (with the corresponding markers).</li>
+</ul>
+<h2 id="from-133-to-134">From 1.3.3 to 1.3.4</h2>
+<p>First, apply SQLs to denormalize LARGE_DATA table from here: [https://issues.apache.org/jira/browse/ODE-694]</p>
+<p>Then, please apply following updates:</p>
+<div class="codehilite"><pre><span class="k">alter</span> <span class="k">table</span> <span class="n">BPEL_XML_DATA</span> <span class="k">add</span> <span class="n">SIMPLE_VALUE</span> <span class="n">varchar2</span><span class="p">(</span><span class="mi">255</span><span class="p">);</span>
+
+<span class="k">create</span> <span class="k">table</span> <span class="n">ODE_JOB_BAK</span> <span class="k">as</span> <span class="k">select</span> <span class="o">*</span> <span class="k">from</span> <span class="n">ODE_JOB</span><span class="p">;</span>
+<span class="k">alter</span> <span class="k">table</span> <span class="n">ODE_JOB</span> <span class="k">add</span> <span class="n">instanceId</span> <span class="nb">number</span><span class="p">(</span><span class="mi">37</span><span class="p">);</span>
+<span class="k">alter</span> <span class="k">table</span> <span class="n">ODE_JOB</span> <span class="k">add</span> <span class="n">mexId</span> <span class="nb">varchar</span><span class="p">(</span><span class="mi">255</span><span class="p">);</span>
+<span class="k">alter</span> <span class="k">table</span> <span class="n">ODE_JOB</span> <span class="k">add</span> <span class="n">processId</span> <span class="nb">varchar</span><span class="p">(</span><span class="mi">255</span><span class="p">);</span>
+<span class="k">alter</span> <span class="k">table</span> <span class="n">ODE_JOB</span> <span class="k">add</span> <span class="k">type</span> <span class="nb">varchar</span><span class="p">(</span><span class="mi">255</span><span class="p">);</span>
+<span class="k">alter</span> <span class="k">table</span> <span class="n">ODE_JOB</span> <span class="k">add</span> <span class="n">channel</span> <span class="nb">varchar</span><span class="p">(</span><span class="mi">255</span><span class="p">);</span>
+<span class="k">alter</span> <span class="k">table</span> <span class="n">ODE_JOB</span> <span class="k">add</span> <span class="n">correlatorId</span> <span class="nb">varchar</span><span class="p">(</span><span class="mi">255</span><span class="p">);</span>
+<span class="k">alter</span> <span class="k">table</span> <span class="n">ODE_JOB</span> <span class="k">add</span> <span class="n">correlationKeySet</span> <span class="nb">varchar</span><span class="p">(</span><span class="mi">255</span><span class="p">);</span>
+<span class="k">alter</span> <span class="k">table</span> <span class="n">ODE_JOB</span> <span class="k">add</span> <span class="n">retryCount</span> <span class="nb">int</span><span class="p">;</span>
+<span class="k">alter</span> <span class="k">table</span> <span class="n">ODE_JOB</span> <span class="k">add</span> <span class="n">inMem</span> <span class="nb">int</span><span class="p">;</span>
+<span class="k">alter</span> <span class="k">table</span> <span class="n">ODE_JOB</span> <span class="k">add</span> <span class="n">priority</span> <span class="nb">int</span><span class="p">;</span>
+<span class="k">alter</span> <span class="k">table</span> <span class="n">ODE_JOB</span> <span class="k">add</span> <span class="n">detailsExt</span> <span class="nb">blob</span><span class="p">;</span>
+<span class="k">update</span> <span class="n">ODE_JOB</span> <span class="n">oj</span> <span class="k">set</span> <span class="n">detailsExt</span> <span class="o">=</span> <span class="p">(</span><span class="k">select</span> <span class="n">details</span> <span class="k">from</span> <span class="n">ODE_JOB</span> <span class="k">where</span> <span class="n">jobid</span> <span class="o">=</span> <span class="n">oj</span><span class="p">.</span><span class="n">jobid</span><span class="p">);</span>
+<span class="k">alter</span> <span class="k">table</span> <span class="n">ODE_JOB</span> <span class="k">drop</span> <span class="k">column</span> <span class="n">details</span><span class="p">;</span>
+</pre></div>
+
+
+<h2 id="from-132-to-133">From 1.3.2 to 1.3.3</h2>
+<p>None</p>
+<h2 id="from-12-to-132">From 1.2 to 1.3.2</h2>
+<p>If you're currently using ODE <em>1.2</em> and are upgrading to 1.3.2, please run the following queries.</p>
+<h3 id="for-openjpa-database-schema">For OpenJPA database schema</h3>
+<div class="codehilite"><pre><span class="k">create</span> <span class="k">table</span> <span class="n">ODE_SCHEMA_VERSION</span> <span class="p">(</span><span class="k">VERSION</span> <span class="nb">integer</span><span class="p">);</span>
+<span class="k">insert</span> <span class="k">into</span> <span class="n">ODE_SCHEMA_VERSION</span> <span class="k">values</span> <span class="p">(</span><span class="mi">5</span><span class="p">);</span>
+
+<span class="k">alter</span> <span class="k">table</span> <span class="n">ODE_MESSAGE_EXCHANGE</span> <span class="k">add</span> <span class="k">column</span> <span class="p">(</span><span class="n">SUBSCRIBER_COUNT</span> <span class="nb">integer</span><span class="p">);</span>
+<span class="k">alter</span> <span class="k">table</span> <span class="n">ODE_MESSAGE_ROUTE</span> <span class="k">add</span> <span class="k">column</span> <span class="p">(</span><span class="n">ROUTE_POLICY</span> <span class="nb">character</span> <span class="nb">varying</span><span class="p">(</span><span class="mi">255</span><span class="p">));</span>
+</pre></div>
+
+
+<h3 id="for-hibernate-database-schema">For Hibernate database schema</h3>
+<p>(Mind the table names)</p>
+<div class="codehilite"><pre><span class="k">create</span> <span class="k">table</span> <span class="n">ODE_SCHEMA_VERSION</span><span class="p">(</span><span class="k">VERSION</span> <span class="nb">integer</span><span class="p">);</span>
+<span class="k">insert</span> <span class="k">into</span> <span class="n">ODE_SCHEMA_VERSION</span> <span class="k">values</span> <span class="p">(</span><span class="mi">5</span><span class="p">);</span>
+
+<span class="k">alter</span> <span class="k">table</span> <span class="n">BPEL_MESSAGE_EXCHANGE</span> <span class="k">add</span> <span class="k">column</span> <span class="p">(</span><span class="n">SUBSCRIBER_COUNT</span> <span class="nb">integer</span><span class="p">);</span>
+<span class="k">alter</span> <span class="k">table</span> <span class="n">BPEL_SELECTORS</span> <span class="k">add</span> <span class="k">column</span> <span class="p">(</span><span class="n">ROUTE_POLICY</span> <span class="nb">character</span> <span class="nb">varying</span><span class="p">(</span><span class="mi">255</span><span class="p">));</span>
+</pre></div>
+
+
+<h2 id="from-11-to-12">From 1.1 to 1.2</h2>
+<p>The upgrade path from 1.1 to 1.2 is relatively simple as there haven't any major change in the database or runtime models. Still, if you use the Hibernate database schema, one column has been added so you will need to execute the following upgrade script (make sure to <em>backup before</em> to prevent any data loss):</p>
+<div class="codehilite"><pre><span class="k">alter</span> <span class="k">table</span> <span class="n">BPEL_SELECTORS</span> <span class="k">add</span> <span class="k">column</span> <span class="p">(</span><span class="n">PROC_TYPE</span> <span class="nb">varchar</span><span class="p">(</span><span class="mi">255</span><span class="p">));</span>
+<span class="k">update</span> <span class="n">BPEL_PROCESS</span> <span class="n">p</span><span class="p">,</span> <span class="n">BPEL_CORRELATOR</span> <span class="k">c</span><span class="p">,</span> <span class="n">BPEL_SELECTORS</span> <span class="n">s</span> <span class="k">set</span> <span class="n">s</span><span class="p">.</span><span class="n">PROC_TYPE</span> <span class="o">=</span> <span class="p">(</span><span class="s1">'{'</span> <span class="o">+</span> <span class="n">p</span><span class="p">.</span><span class="n">type_ns</span> <span class="o">+</span> <span class="s1">'}'</span> <span class="o">+</span> <span class="n">p</span><span class="p">.</span><span class="n">type_name</span><span class="p">)</span> <span class="k">where</span> <span class="n">s</span><span class="p">.</span><span class="n">CORRELATOR</span> <span class="o">=</span> <span class="k">c</span><span class="p">.</span><span class="n">CID</span> <span class="k">and</spa
n> <span class="k">c</span><span class="p">.</span><span class="n">PROCESS_ID</span> <span class="o">=</span> <span class="n">p</span><span class="p">.</span><span class="n">PROCID</span><span class="p">;</span>
+</pre></div>
+
+
+<p>The update statement is only necessary if you have currently running instances. Note that if you're using the default OpenJPA database schema, no database modifications are necessary. Once this is done, it's fairly simple:</p>
+<ul>
+<li>Redeploy your new ODE 1.2 WAR.</li>
+<li>Copy all the previous configuration and deployed processes (with the corresponding markers).</li>
+</ul>
+<p>That's it!</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/war-deployment.html
==============================================================================
--- websites/staging/ode/trunk/content/userguide/war-deployment.html (added)
+++ websites/staging/ode/trunk/content/userguide/war-deployment.html Tue Dec 11 12:48:20 2012
@@ -0,0 +1,178 @@
+<!DOCTYPE html>
+<html>
+ <head>
+ <title>WAR Deployment</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="/user-guide.html">User Guide</a></li>
+ <li><a href="/developer-guide.html">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="/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>WAR Deployment</h1>
+
+ </div>
+ </header>
+
+
+ <!-- Content -->
+ <div class="container">
+
+ <div class="row">
+ <div class="span12">
+ <p><a name="WARDeployment-DeployingtheWAR"></a></p>
+<h2 id="deploying-the-war">Deploying the WAR</h2>
+<p>Unzip the <a href="getting-ode.html">distribution</a> somewhere on your disk, everything needed is inside.</p>
+<p>Get the WAR file in the distribution root directory, rename it to <em>ode.war</em> and copy this file to <a href="http://tomcat.apache.org">Tomcat</a>'s webapp directory. Start Tomcat and ODE should be up and running. You should get the <a href="http://ws.apache.org/axis2">Axis2</a> welcome page under <a href="http://localhost:8080/ode">http://localhost:8080/ode</a>. The ODE WAR includes its own embedded database (<a href="http://db.apache.org/derby">Derby</a>) so you don't have to worry about configuring any external database for now.</p>
+<p><a name="WARDeployment-Examples"></a></p>
+<h3 id="examples">Examples</h3>
+<p>Copy the content of the <em>examples</em> directory in the distribution (the 3 sub-directories) to <em>tomcat/webapps/ode/WEB-INF/processes</em>, this will automatically deploy the 3 example processes. Use the sendsoap command located in the distribution <em>bin</em> directory to send test messages. The messages to run each of the 3 examples are provided in their respective directory (testRequest.soap). For each example type something like:</p>
+<div class="codehilite"><pre>bin/sendsoap http://localhost:8080/ode/processes/helloWorld examples/HelloWorld2/testRequest.soap
+</pre></div>
+
+
+<p>The <em>sendsoap</em> executable can be found in the distribution <em>bin</em> directory. The urls should be updated according to the address defined in the WSDL file for the process service.</p>
+<p><a name="WARDeployment-ConfiguringODEinTomcatwithaMySQLdatabase"></a></p>
+<h3 id="configuring-ode-in-tomcat-with-a-mysql-database">Configuring ODE in Tomcat with a MySQL database</h3>
+<p>The ODE war should have been copied to the <em>webapps</em> directory of Tomcat and the server should have been started at least once before following these instructions. This ensures that the webapp is properly exploded.</p>
+<ol>
+<li>Drop the MySQL JDBC driver (<a href="http://dev.mysql.com/downloads/#connector-j">MySQL Connector/J</a>) in the <em>common/lib</em> directory of Tomcat.</li>
+<li>
+<p>Add the following stanza to <em>conf/server.xml</em> inside the <Host> element:</p>
+<div class="codehilite"><pre><span class="nt"><Context</span> <span class="na">path=</span><span class="s">"/ode"</span> <span class="na">docBase=</span><span class="s">"ode"</span> <span class="na">debug=</span><span class="s">"5"</span> <span class="na">reloadable=</span><span class="s">"true"</span> <span class="na">crossContext=</span><span class="s">"true"</span><span class="nt">></span>
+ <span class="nt"><Resource</span> <span class="na">name=</span><span class="s">"jdbc/ODEDB"</span> <span class="na">auth=</span><span class="s">"Container"</span> <span class="na">type=</span><span class="s">"javax.sql.DataSource"</span>
+ <span class="na">maxActive=</span><span class="s">"100"</span> <span class="na">maxIdle=</span><span class="s">"30"</span> <span class="na">maxWait=</span><span class="s">"10000"</span>
+ <span class="na">username=</span><span class="s">"root"</span> <span class="na">password=</span><span class="s">""</span> <span class="na">driverClassName=</span><span class="s">"com.mysql.jdbc.Driver"</span>
+ <span class="na">url=</span><span class="s">"jdbc:mysql://localhost:3306/ode?autoReconnect=true"</span><span class="nt">/></span>
+<span class="nt"></Context></span>
+</pre></div>
+
+
+</li>
+<li>
+<p>Make sure that MySQL is started and the <a href="^ode_openjpa_mysql-1.3.2.sql.html">ODE schema</a> has been loaded in a <em>ode</em> database.</p>
+<div class="codehilite"><pre>$ mysql -u root
+mysql> create database ode;
+mysql> exit
+$ mysql -u root ode < ode_openjpa_mysql-1.3.2.sql
+</pre></div>
+
+
+</li>
+<li>
+<p>Add a file named <em>ode-axis2.properties</em> under <em>webapps/ode/WEB-INF/conf</em> with the following content:</p>
+<div class="codehilite"><pre>ode-axis2.db.mode=EXTERNAL
+ode-axis2.db.ext.dataSource=java:comp/env/jdbc/ODEDB
+</pre></div>
+
+
+</li>
+</ol>
+<p>You're done!</p>
+<p><a name="WARDeployment-ConfiguringODEinJBosswithJNDIEXTERNALdatasource"></a></p>
+<h2 id="configuring-ode-in-jboss-with-jndi-external-datasource">Configuring ODE in JBoss with JNDI EXTERNAL datasource</h2>
+<p>Create ode/WEB-INF/conf/ode-axis2.properties with following content:</p>
+<div class="codehilite"><pre>#Uncomment for using dao hibernate
+#ode-axis2.dao.factory=org.apache.ode.daohib.bpel.BpelDAOConnectionFactoryImpl
+ode-axis2.db.mode=EXTERNAL
+ode-axis2.db.ext.dataSource=java:comp/env/jdbc/ode
+ode-axis2.event.listeners=org.apache.ode.bpel.common.evt.DebugBpelEventListener
+ode-axis2.tx.factory.class=org.apache.ode.axis2.util.JBossFactory
+</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