Author: buildbot
Date: Mon Dec 31 17:26:46 2012
New Revision: 844441
Log:
Staging update by buildbot for ode
Modified:
websites/staging/ode/trunk/content/ (props changed)
websites/staging/ode/trunk/content/faq.html
websites/staging/ode/trunk/content/ws-security-in-ode.html
Propchange: websites/staging/ode/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Dec 31 17:26:46 2012
@@ -1 +1 @@
-1427189
+1427192
Modified: websites/staging/ode/trunk/content/faq.html
==============================================================================
--- websites/staging/ode/trunk/content/faq.html (original)
+++ websites/staging/ode/trunk/content/faq.html Mon Dec 31 17:26:46 2012
@@ -89,7 +89,7 @@
<p><strong>Q.</strong> <em>What is ODE?</em>
<strong>A.</strong> ODE is a system for executing reliable long-running
process described using the WS-BPEL 2.0 standard and the BPEL4WS 1.1 vendor
specification.</p>
<p><strong>Q.</strong> <em>What is the architecture of ODE?</em>
-<strong>A.</strong> The architecture of ODE is described in the ODE <a
href="architectural-overview.html">Architectural Overview</a></p>
+<strong>A.</strong> The architecture of ODE is described in the ODE <a
href="/developerguide/architectural-overview.html">Architectural
Overview</a></p>
<p><strong>Q.</strong> <em>In what language is ODE written?</em>
<strong>A.</strong> ODE is written in Java and relies on JDK v5.0 features.</p>
<p><strong>Q.</strong> <em>How does ODE ensure reliable process execution?</em>
@@ -134,7 +134,7 @@
<p><strong>Q.</strong> <em>Does ODE require a database? Which databases and
versions does ODE support?</em>
<strong>A.</strong> ODE does not depend directly on any specific database or
persistence mechanism. Instead, ODE relies on a set of data access object
("DAO") interfaces that encapsulate the behaviors of a persistence layer. The
ODE distribution includes a DAO implementation for JDBC databases built using
<a href="http://openjpa.apache.org";>OpenJPA</a>. This DAO implementation can
support most common relational databases. Schemas suitable for <a
href="http://www.mysql.com";>MySQL</a> and <a
href="http://db.apache.org/derby/";>Derby</a> are provided. Relational databases
lacking transaction or binary large object ("BLOB") capabilities are not
supported. The DAO interfaces can readily be implemented to support alternative
persistence mechanisms (e.g. JDO), XML datastores, or direct filesystem-based
persistence.</p>
<p><strong>Q.</strong> <em>Does ODE require a J2EE application server?</em>
-<strong>A.</strong> The core ODE components do not require a J2EE application
server. ODE relies on a <a
href="http://svn.apache.org/repos/asf/ode/trunk/bpel-api/src/main/java/org/apache/ode/bpel/iapi/";>Integration
API</a> that allows ODE to be embedded in most any environment that can supply
the required facilities. An <a
href="architectural-overview.html#ODEIntegrationLayers">AXIS2 Integration</a>
is provided that permits ODE to be installed on a J2EE application server, or
in a "dumb" Servlet container via a WAR file. A <a
href="architectural-overview.html#ODEIntegrationLayers">JBI Integration</a>
integration is also provided that permits ODE to be installed in a JBI
container.</p>
+<strong>A.</strong> The core ODE components do not require a J2EE application
server. ODE relies on a <a
href="http://svn.apache.org/repos/asf/ode/trunk/bpel-api/src/main/java/org/apache/ode/bpel/iapi/";>Integration
API</a> that allows ODE to be embedded in most any environment that can supply
the required facilities. An <a
href="/developerguide/architectural-overview.html#ODEIntegrationLayers">AXIS2
Integration</a> is provided that permits ODE to be installed on a J2EE
application server, or in a "dumb" Servlet container via a WAR file. A <a
href="/developerguide/architectural-overview.html#ODEIntegrationLayers">JBI
Integration</a> integration is also provided that permits ODE to be installed
in a JBI container.</p>
<p><strong>Q.</strong> <em>Is there a stand-alone ODE integration?</em>
<strong>A.</strong> No, the standard ODE distributions require either an
application server, Servlet container, or JBI container.</p>
<p><strong>Q.</strong> <em>Can ODE be deployed within an application server or
web container?</em>
@@ -148,7 +148,7 @@
<h2 id="integration-with-third-party-products">Integration with Third-Party
Products</h2>
<p>This section covers frequently asked questions related to integrating ODE
into third-party products or integrating third-party products into ODE.</p>
<p><strong>Q.</strong> <em>Can ODE interact directly (i.e., not over the
network) with native Java services?</em>
-<strong>A.</strong> This is currently supported in the <a
href="architectural-overview.html#ODEIntegrationLayers">JBI Integration</a> via
standard JBI mechanisms. It is currently not supported in the <a
href="architectural-overview.html#ODEIntegrationLayers">AXIS2 Integration</a>
but will be in the future.</p>
+<strong>A.</strong> This is currently supported in the <a
href="/developerguide/architectural-overview.html#ODEIntegrationLayers">JBI
Integration</a> via standard JBI mechanisms. It is currently not supported in
the <a
href="/developerguide/architectural-overview.html#ODEIntegrationLayers">AXIS2
Integration</a> but will be in the future.</p>
<p><strong>Q.</strong> <em>Can ODE integrate with Middleware X? Can ODE
integrate with Legacy system Y? Can ODE integrate with Enterprise Application
Z? How is this accomplished?</em>
<strong>A.</strong> The generic answer is "Yes," although it requires some
work on the part of the integrator. The primary extension point for integrating
with external systems is the <a
href="http://ode.apache.org/javadoc/org/apache/ode/bpel/pmapi/ProcessManagement.html";>Integration
API</a>, which can be used to embed ODE in most any environment.</p>
<p><strong>Q.</strong> <em>Does ODE rely on any third-party or open source
libraries?</em>
@@ -156,13 +156,13 @@
<h2 id="ode-and-web-services">ODE and Web Services</h2>
<p>This section covers frequently asked questions about how ODE related to
various web services specifications and initiatives.</p>
<p><strong>Q.</strong> <em>Does ODE supply a SOAP stack?</em>
-<strong>A.</strong> Not directly. ODE relies on the <a
href="architectural-overview.html#ODEIntegrationLayers">Integration Layer</a>
to supply the "physical" communication mechanisms. The <a
href="architectural-overview.html#ODEIntegrationLayers">AXIS2 Integration
Layer</a> that is part of the ODE distribution uses the AXIS2 SOAP stack. The
<a href="architectural-overview.html#ODEIntegrationLayers">JBI Integration
Layer</a> relies on external HTTP/SOAP components (e.g. ServiceMix's
<code>servicemix-http</code> component).</p>
+<strong>A.</strong> Not directly. ODE relies on the <a
href="/developerguide/architectural-overview.html#ODEIntegrationLayers">Integration
Layer</a> to supply the "physical" communication mechanisms. The <a
href="/developerguide/architectural-overview.html#ODEIntegrationLayers">AXIS2
Integration Layer</a> that is part of the ODE distribution uses the AXIS2 SOAP
stack. The <a
href="/developerguide/architectural-overview.html#ODEIntegrationLayers">JBI
Integration Layer</a> relies on external HTTP/SOAP components (e.g.
ServiceMix's <code>servicemix-http</code> component).</p>
<p><strong>Q.</strong> <em>Can ODE be integrated with third-party web services
products such as Apache AXIS, Systinet WASP, or JAXRPC?</em>
<strong>A.</strong> Yes, ODE can be integrated into most any stack via the <a
href="http://incubator.apache.org/ode/javadoc/bpel-api/index.html";>Integration
API</a></p>
<p><strong>Q.</strong> <em>Does ODE support web services transaction
specifications, e.g., WS-Transaction, WS-Coordination, WS-Business Activity,
OASIS BTP, or Composite Application Framework (WS-CAF)?</em>
<strong>A.</strong> No, not at present.</p>
<p><strong>Q.</strong> <em>Does ODE support WS-Addressing?</em>
-<strong>A.</strong> ODE does not directly support WS-Addressing. However, the
BPEL implementation and the core ODE infrastructure provides support for opaque
end-point references. This allows ODE to be integrated with arbitrary
addressing standards. The <a
href="architectural-overview.html#ODEIntegrationLayers">AXIS2 Integration
Layer</a> for ODE employs this mechanism to support WS-Addressing.</p>
+<strong>A.</strong> ODE does not directly support WS-Addressing. However, the
BPEL implementation and the core ODE infrastructure provides support for opaque
end-point references. This allows ODE to be integrated with arbitrary
addressing standards. The <a
href="/developerguide/architectural-overview.html#ODEIntegrationLayers">AXIS2
Integration Layer</a> for ODE employs this mechanism to support
WS-Addressing.</p>
<h2 id="reliability">Reliability</h2>
<p>This section covers frequently asked questions about the reliability of
ODE.</p>
<p><strong>Q.</strong> <em>Can ODE recover in the event of system failure?</em>
Modified: websites/staging/ode/trunk/content/ws-security-in-ode.html
==============================================================================
--- websites/staging/ode/trunk/content/ws-security-in-ode.html (original)
+++ websites/staging/ode/trunk/content/ws-security-in-ode.html Mon Dec 31
17:26:46 2012
@@ -114,7 +114,7 @@
<div class="alert alert-warning"><h4 class="alert-heading">Only in
1.3.2+</h4></div>
<p>ODE 1.3.2 introduces support for WS-Security: secure services can now be
invoked from a process, and the process service itself might be secured. A
first part will explain how to invoke a secured service, a second part how to
secure the process service.</p>
-<p>ODE has an <a
href="architectural-overview.html#ODE-Integration-Layers">Integration Layer
based on Axis2</a> so using Rampart, the Axis2 security modules, goes without
saying. As a result this section will only focus on Rampart integration.
Rampart and WS-Security specifications won't be detailed here. Please refer to
their ad-hoc documentations for further details.</p>
+<p>ODE has an <a
href="/developerguide/architectural-overview.html#ODE-Integration-Layers">Integration
Layer based on Axis2</a> so using Rampart, the Axis2 security modules, goes
without saying. As a result this section will only focus on Rampart
integration. Rampart and WS-Security specifications won't be detailed here.
Please refer to their ad-hoc documentations for further details.</p>
<h3 id="quick-rampart-introduction">Quick Rampart introduction</h3>
<p>As any other Axis2 module, Rampart is configurable with <a
href="http://ws.apache.org/axis2/1_0/axis2config.html#Service_Configuration";>Axis2
Service configuration files</a>. For instance a service.xml document, using
the parameter based configuration model, might be:</p>
<div class="codehilite"><pre><span class="nt"><service></span>
