You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@ode.apache.org by va...@apache.org on 2012/12/28 16:59:01 UTC
svn commit: r1426554 - in /ode/site/trunk/content:
extensions/wsdl-11-extensions-for-rest.mdtext ws-security-in-ode.mdtext
Author: vanto
Date: Fri Dec 28 15:59:01 2012
New Revision: 1426554
URL: http://svn.apache.org/viewvc?rev=1426554&view=rev
Log:
link fixes.
Modified:
ode/site/trunk/content/extensions/wsdl-11-extensions-for-rest.mdtext
ode/site/trunk/content/ws-security-in-ode.mdtext
Modified: ode/site/trunk/content/extensions/wsdl-11-extensions-for-rest.mdtext
URL: http://svn.apache.org/viewvc/ode/site/trunk/content/extensions/wsdl-11-extensions-for-rest.mdtext?rev=1426554&r1=1426553&r2=1426554&view=diff
==============================================================================
--- ode/site/trunk/content/extensions/wsdl-11-extensions-for-rest.mdtext (original)
+++ ode/site/trunk/content/extensions/wsdl-11-extensions-for-rest.mdtext Fri Dec 28 15:59:01 2012
@@ -226,7 +226,7 @@ A failure is thrown if the code is one o
</tbody>
</table>
-<div class="alert alert-info">Note that 3xx errors should be pretty rare since by default the first hundred redirections are followed. You can tweak this value by setting the property <code>http.protocol.max-redirects</code> in the <a href="endpoint-configuration.html">enpoint-configuration.properties</a> of your process.</div>
+<div class="alert alert-info">Note that 3xx errors should be pretty rare since by default the first hundred redirections are followed. You can tweak this value by setting the property <code>http.protocol.max-redirects</code> in the <a href="/endpoint-configuration.html">enpoint-configuration.properties</a> of your process.</div>
Here what ODE does, if the status code is one of those listed in the next table (500, 501, etc):
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=1426554&r1=1426553&r2=1426554&view=diff
==============================================================================
--- ode/site/trunk/content/ws-security-in-ode.mdtext (original)
+++ ode/site/trunk/content/ws-security-in-ode.mdtext Fri Dec 28 15:59:01 2012
@@ -92,7 +92,7 @@ Another example using WS-Security Policy
</service>
-The important thing to notice is that these documents are plain [Axis2 Service configuration files](http://ws.apache.org/axis2/1_0/axis2config.html#Service_Configuration). And as explained in the [ODE User Guide](endpoint-Configuration.html#Additional-Configuration-for-SOAP-Endpoints), a mechanism to handle these files already exists. So all we have to do is reuse this mechanism, the rest is pure Rampart configuration.
+The important thing to notice is that these documents are plain [Axis2 Service configuration files](http://ws.apache.org/axis2/1_0/axis2config.html#Service_Configuration). And as explained in the [ODE User Guide](endpoint-configuration.html#Additional-Configuration-for-SOAP-Endpoints), a mechanism to handle these files already exists. So all we have to do is reuse this mechanism, the rest is pure Rampart configuration.
Let's take an example and see the actual required steps.