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 13:37:51 UTC
svn commit: r1426478 -
/ode/site/trunk/content/wsdl-11-extensions-for-rest.mdtext
Author: vanto
Date: Fri Dec 28 12:37:50 2012
New Revision: 1426478
URL: http://svn.apache.org/viewvc?rev=1426478&view=rev
Log:
fix formatting
Modified:
ode/site/trunk/content/wsdl-11-extensions-for-rest.mdtext
Modified: ode/site/trunk/content/wsdl-11-extensions-for-rest.mdtext
URL: http://svn.apache.org/viewvc/ode/site/trunk/content/wsdl-11-extensions-for-rest.mdtext?rev=1426478&r1=1426477&r2=1426478&view=diff
==============================================================================
--- ode/site/trunk/content/wsdl-11-extensions-for-rest.mdtext (original)
+++ ode/site/trunk/content/wsdl-11-extensions-for-rest.mdtext Fri Dec 28 12:37:50 2012
@@ -1,5 +1,7 @@
Title: WSDL 1.1 Extensions for REST
+## Overview
+
The [Resource-Oriented Architecture](http://en.wikipedia.org/wiki/Representational_State_Transfer) defines four concepts:
1. Resources
@@ -198,12 +200,31 @@ Another domain completely neglected by W
ODE allows you to bind a fault with HTTP Binding. If a [4xx or a 5xx](http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4) is returned, the following logic is applied:
A failure is thrown if the code is one of these:
-|| Status-Codes triggering a Failure ||
-| 3xx Redirections |
-|401_UNAUTHORIZED|
-|408_REQUEST_TIMEOUT|
-|503_SERVICE_UNAVAILABLE|
-|504_GATEWAY_TIMEOUT|
+
+<table>
+ <thead>
+ <tr>
+ <th>Status-Codes triggering a Failure</th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>3xx Redirections</td>
+ </tr>
+ <tr>
+ <td>401_UNAUTHORIZED</td>
+ </tr>
+ <tr>
+ <td>408_REQUEST_TIMEOUT</td>
+ </tr>
+ <tr>
+ <td>503_SERVICE_UNAVAILABLE</td>
+ </tr>
+ <tr>
+ <td>504_GATEWAY_TIMEOUT</td>
+ </tr>
+ </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>
@@ -216,17 +237,18 @@ Here what ODE does, if the status code i
If so far everything is fine, the HTTP response body is parsed into an xml document. Then the fault to be thrown is inferred from the qname of the response root element, i.e the fault having a message part matching the root element. This matching process is exactly the same as for a SOAP service.
If one of these steps fails, a failure is thrown.
-|| Status-Codes that may trigger a Fault ||if the body element matches a fault declaration||
-|500_INTERNAL_SERVER_ERROR | 407_PROXY_AUTHENTICATION_REQUIRED |
-|501_NOT_IMPLEMENTED | 409_CONFLICT |
-|502_BAD_GATEWAY | 410_GONE |
-|505_HTTP_VERSION_NOT_SUPPORTED | 412_PRECONDITION_FAILED |
-|400_BAD_REQUEST | 413_REQUEST_TOO_LONG |
-|402_PAYMENT_REQUIRED | 414_REQUEST_URI_TOO_LONG |
-|403_FORBIDDEN | 415_UNSUPPORTED_MEDIA_TYPE |
-|404_NOT_FOUND | 411_LENGTH_REQUIRED |
-|405_METHOD_NOT_ALLOWED | 416_REQUESTED_RANGE_NOT_SATISFIABLE |
-|406_NOT_ACCEPTABLE | 417_EXPECTATION_FAILED |
+Status-Codes that may trigger a Fault |if the body element matches a fault declaration
+-----------------------------------------------------------------------------------------
+500_INTERNAL_SERVER_ERROR | 407_PROXY_AUTHENTICATION_REQUIRED
+501_NOT_IMPLEMENTED | 409_CONFLICT
+502_BAD_GATEWAY | 410_GONE
+505_HTTP_VERSION_NOT_SUPPORTED | 412_PRECONDITION_FAILED
+400_BAD_REQUEST | 413_REQUEST_TOO_LONG
+402_PAYMENT_REQUIRED | 414_REQUEST_URI_TOO_LONG
+403_FORBIDDEN | 415_UNSUPPORTED_MEDIA_TYPE
+404_NOT_FOUND | 411_LENGTH_REQUIRED
+405_METHOD_NOT_ALLOWED | 416_REQUESTED_RANGE_NOT_SATISFIABLE
+406_NOT_ACCEPTABLE | 417_EXPECTATION_FAILED
Note that you can't bind a given fault to a specific status code.