svn commit: r1427192 - in /ode/site/trunk/content: faq.mdtext ws-security-in-ode.mdtext

[va...@apache.org]

Author: vanto
Date: Mon Dec 31 17:26:41 2012
New Revision: 1427192

URL: http://svn.apache.org/viewvc?rev=1427192&view=rev
Log:
fixing broken link.

Modified:
    ode/site/trunk/content/faq.mdtext
    ode/site/trunk/content/ws-security-in-ode.mdtext

Modified: ode/site/trunk/content/faq.mdtext
URL: http://svn.apache.org/viewvc/ode/site/trunk/content/faq.mdtext?rev=1427192&r1=1427191&r2=1427192&view=diff
==============================================================================
--- ode/site/trunk/content/faq.mdtext (original)
+++ ode/site/trunk/content/faq.mdtext Mon Dec 31 17:26:41 2012
@@ -10,7 +10,7 @@ __Q.__ _What is ODE?_
 __A.__ 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.
 
 __Q.__ _What is the architecture of ODE?_
-__A.__ The architecture of ODE is described in the ODE [Architectural Overview](architectural-overview.html)
+__A.__ The architecture of ODE is described in the ODE [Architectural Overview](/developerguide/architectural-overview.html)
 
 
 __Q.__ _In what language is ODE written?_
@@ -82,7 +82,7 @@ __Q.__ _Does ODE require a database? Whi
 __A.__ 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 [OpenJPA](http://openjpa.apache.org). This DAO implementation can support most common relational databases. Schemas suitable for [MySQL](http://www.mysql.com) and [Derby](http://db.apache.org/derby/) 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.
 
 __Q.__ _Does ODE require a J2EE application server?_
-__A.__ The core ODE components do not require a J2EE application server. ODE relies on a [Integration API](http://svn.apache.org/repos/asf/ode/trunk/bpel-api/src/main/java/org/apache/ode/bpel/iapi/) that allows ODE to be embedded in most any environment that can supply the required facilities. An [AXIS2 Integration](architectural-overview.html#ODEIntegrationLayers) is provided that permits ODE to be installed on a J2EE application server, or in a "dumb" Servlet container via a WAR file. A [JBI Integration](architectural-overview.html#ODEIntegrationLayers) integration is also provided that permits ODE to be installed in a JBI container.
+__A.__ The core ODE components do not require a J2EE application server. ODE relies on a [Integration API](http://svn.apache.org/repos/asf/ode/trunk/bpel-api/src/main/java/org/apache/ode/bpel/iapi/) that allows ODE to be embedded in most any environment that can supply the required facilities. An [AXIS2 Integration](/developerguide/architectural-overview.html#ODEIntegrationLayers) is provided that permits ODE to be installed on a J2EE application server, or in a "dumb" Servlet container via a WAR file. A [JBI Integration](/developerguide/architectural-overview.html#ODEIntegrationLayers) integration is also provided that permits ODE to be installed in a JBI container.
 
 __Q.__ _Is there a stand-alone ODE integration?_
 __A.__ No, the standard ODE distributions require either an application server, Servlet container, or JBI container.
@@ -104,7 +104,7 @@ __A.__ We try to use sensible sizes for 
 This section covers frequently asked questions related to integrating ODE into third-party products or integrating third-party products into ODE.
 
 __Q.__ _Can ODE interact directly (i.e., not over the network) with native Java services?_
-__A.__ This is currently supported in the [JBI Integration](architectural-overview.html#ODEIntegrationLayers) via standard JBI mechanisms. It is currently not supported in the [AXIS2 Integration](architectural-overview.html#ODEIntegrationLayers) but will be in the future.
+__A.__ This is currently supported in the [JBI Integration](/developerguide/architectural-overview.html#ODEIntegrationLayers) via standard JBI mechanisms. It is currently not supported in the [AXIS2 Integration](/developerguide/architectural-overview.html#ODEIntegrationLayers) but will be in the future.
 
 __Q.__ _Can ODE integrate with Middleware X? Can ODE integrate with Legacy system Y? Can ODE integrate with Enterprise Application Z? How is this accomplished?_
 __A.__ 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 [Integration API](http://ode.apache.org/javadoc/org/apache/ode/bpel/pmapi/ProcessManagement.html), which can be used to embed ODE in most any environment.
@@ -117,7 +117,7 @@ __A.__ ODE uses a number of liberally-li
 This section covers frequently asked questions about how ODE related to various web services specifications and initiatives.
 
 __Q.__ _Does ODE supply a SOAP stack?_
-__A.__ Not directly. ODE relies on the [Integration Layer](architectural-overview.html#ODEIntegrationLayers) to supply the "physical" communication mechanisms. The [AXIS2 Integration Layer](architectural-overview.html#ODEIntegrationLayers) that is part of the ODE distribution uses the AXIS2 SOAP stack. The [JBI Integration Layer](architectural-overview.html#ODEIntegrationLayers) relies on external HTTP/SOAP components (e.g. ServiceMix's `servicemix-http` component).
+__A.__ Not directly. ODE relies on the [Integration Layer](/developerguide/architectural-overview.html#ODEIntegrationLayers) to supply the "physical" communication mechanisms. The [AXIS2 Integration Layer](/developerguide/architectural-overview.html#ODEIntegrationLayers) that is part of the ODE distribution uses the AXIS2 SOAP stack. The [JBI Integration Layer](/developerguide/architectural-overview.html#ODEIntegrationLayers) relies on external HTTP/SOAP components (e.g. ServiceMix's `servicemix-http` component).
 
 __Q.__ _Can ODE be integrated with third-party web services products such as Apache AXIS, Systinet WASP, or JAXRPC?_
 __A.__ Yes, ODE can be integrated into most any stack via the [Integration API](http://incubator.apache.org/ode/javadoc/bpel-api/index.html)
@@ -128,7 +128,7 @@ __Q.__ _Does ODE support web services tr
 __A.__ No, not at present.
 
 __Q.__ _Does ODE support WS-Addressing?_
-__A.__ 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 [AXIS2 Integration Layer](architectural-overview.html#ODEIntegrationLayers) for ODE employs this mechanism to support WS-Addressing.
+__A.__ 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 [AXIS2 Integration Layer](/developerguide/architectural-overview.html#ODEIntegrationLayers) for ODE employs this mechanism to support WS-Addressing.
 
 ## Reliability
 

Modified: ode/site/trunk/content/ws-security-in-ode.mdtext
URL: http://svn.apache.org/viewvc/ode/site/trunk/content/ws-security-in-ode.mdtext?rev=1427192&r1=1427191&r2=1427192&view=diff
==============================================================================
--- ode/site/trunk/content/ws-security-in-ode.mdtext (original)
+++ ode/site/trunk/content/ws-security-in-ode.mdtext Mon Dec 31 17:26:41 2012
@@ -10,7 +10,7 @@ Category: documentation
 
 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.
 
-ODE has an [Integration Layer based on Axis2](architectural-overview.html#ODE-Integration-Layers) 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.
+ODE has an [Integration Layer based on Axis2](/developerguide/architectural-overview.html#ODE-Integration-Layers) 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.
 
 ### Quick Rampart introduction