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/28 12:21:56 UTC
svn commit: r844090 - in /websites/staging/ode/trunk/content: ./ assign.html
faq.html management-api.html pxe-deploy-command.html receive.html
sendsoap-command.html wsdl-11-extensions-for-rest.html
wsdl-11-http-binding-support.html
Author: buildbot
Date: Fri Dec 28 11:21:56 2012
New Revision: 844090
Log:
Staging update by buildbot for ode
Modified:
websites/staging/ode/trunk/content/ (props changed)
websites/staging/ode/trunk/content/assign.html
websites/staging/ode/trunk/content/faq.html
websites/staging/ode/trunk/content/management-api.html
websites/staging/ode/trunk/content/pxe-deploy-command.html
websites/staging/ode/trunk/content/receive.html
websites/staging/ode/trunk/content/sendsoap-command.html
websites/staging/ode/trunk/content/wsdl-11-extensions-for-rest.html
websites/staging/ode/trunk/content/wsdl-11-http-binding-support.html
Propchange: websites/staging/ode/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Dec 28 11:21:56 2012
@@ -1 +1 @@
-1426454
+1426457
Modified: websites/staging/ode/trunk/content/assign.html
==============================================================================
--- websites/staging/ode/trunk/content/assign.html (original)
+++ websites/staging/ode/trunk/content/assign.html Fri Dec 28 11:21:56 2012
@@ -102,7 +102,7 @@
</extensionAssignOperation>
)+
</assign></p>
-<div class="codehilite"><pre><span class="o">*</span><span class="n">throws</span><span class="o">*</span> <span class="p">{{[</span><span class="n">bpel:invalidVariables</span><span class="p">](</span><span class="c1">#invalidVariables)}}, {{[bpel:selectionFailure|#selectionFailure]}}, {{[bpel:subLanguageExecutionFault|#subLanguageExecutionFault]}}, {{[bpel:uninitializedVariable|#uninitializedVariable]}}, {{[bpel:mismatchedAssignmentFailure|#mismatchedAssignmentFailure]}}, {{[bpel:uninitializedPartnerRole|#uninitializedPartnerRole]}}</span>
+<div class="codehilite"><pre><span class="o">*</span><span class="n">throws</span><span class="o">*</span> <span class="p">{{[</span><span class="n">bpel:invalidVariables</span><span class="p">](</span><span class="c1">#invalidVariables)}}, {{[bpel:selectionFailure](#selectionFailure)}}, {{[bpel:subLanguageExecutionFault](#subLanguageExecutionFault)}}, {{[bpel:uninitializedVariable](#uninitializedVariable)}}, {{[bpel:mismatchedAssignmentFailure](#mismatchedAssignmentFailure)}}, {{[bpel:uninitializedPartnerRole](#uninitializedPartnerRole)}}</span>
<span class="n">h3</span><span class="o">.</span> <span class="n">Description</span>
<span class="n">The</span> <span class="p">{{</span><span class="sr"><assign></span><span class="p">}}</span> <span class="n">activity</span> <span class="n">can</span> <span class="n">be</span> <span class="n">used</span> <span class="n">to</span> <span class="n">copy</span> <span class="n">data</span> <span class="n">from</span> <span class="n">one</span> <span class="n">variable</span> <span class="n">to</span> <span class="n">another</span><span class="p">,</span> <span class="n">as</span> <span class="n">well</span> <span class="n">as</span> <span class="n">to</span> <span class="n">construct</span> <span class="ow">and</span> <span class="n">insert</span> <span class="k">new</span> <span class="n">data</span> <span class="n">using</span> <span class="n">expressions</span><span class="o">.</span> <span class="n">The</span> <span class="p">{{</span><span class="sr"><assign></span><span class="p">}}</span> <span class="n">activity</span> <span class="n">can</s
pan> <span class="n">also</span> <span class="n">be</span> <span class="n">used</span> <span class="n">to</span> <span class="n">copy</span> <span class="n">endpoint</span> <span class="n">references</span> <span class="n">to</span> <span class="ow">and</span> <span class="n">from</span> <span class="n">partnerLinks</span><span class="o">.</span>
Modified: websites/staging/ode/trunk/content/faq.html
==============================================================================
--- websites/staging/ode/trunk/content/faq.html (original)
+++ websites/staging/ode/trunk/content/faq.html Fri Dec 28 11:21:56 2012
@@ -132,7 +132,7 @@
<p><strong>Q.</strong> <em>Which operating systems does ODE support?</em>
<strong>A.</strong> ODE is written entirely in Java and can run on any operating system supporting the required Java environment. ODE has been tested and is known to run on Windows 2000, Windows XP, Linux, MacOS X, Solaris, and AIX.</p>
<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 [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.</p>
+<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 [AXIS2 Integration] 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] 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>
Modified: websites/staging/ode/trunk/content/management-api.html
==============================================================================
--- websites/staging/ode/trunk/content/management-api.html (original)
+++ websites/staging/ode/trunk/content/management-api.html Fri Dec 28 11:21:56 2012
@@ -85,12 +85,12 @@
<div class="span12">
<p>ODE has a complete management API to check which processes are deployed, running and completed instances, variables values and more. To see which methods are available, have a look at the <a href="http://ode.apache.org/javadoc/org/apache/ode/bpel/pmapi/ProcessManagement.html">ProcessManagement</a> and <a href="http://ode.apache.org/javadoc/org/apache/ode/bpel/pmapi/InstanceManagement.html">InstanceManagement</a> interfaces, the javadoc is pretty comprehensive.</p>
<p>These two interfaces are available as web services on the Axis2-based distribution. The corresponding WSDL can be found <a href="http://svn.apache.org/repos/asf/ode/trunk/axis2/src/main/wsdl/pmapi.wsdl">here</a>.</p>
-<p>To invoke these two services, any web service client should work (in a perfect interoperable world). To ease the invocation when using an Axis2 client, a helper class is bundled in ode-axis2.jar: <a href="http://ode.apache.org/javadoc/axis2/org/apache/ode/axis2/service/ServiceClientUtil.html">ServiceClientUtil</a>. Usage examples are also available in test classes <a href="http://svn.apache.org/repos/asf/ode/trunk/axis2/src/test/java/org/apache/ode/axis2/management/InstanceManagementTest.java">InstanceManagementTest</a> and [ProcessManagementTest|http://svn.apache.org/repos/asf/ode/trunk/axis2/src/test/java/org/apache/ode/axis2/management/ProcessManagementTest.java]. Here is a short example demonstrating the invocation of the <em>listAllProcesses</em> operation:
+<p>To invoke these two services, any web service client should work (in a perfect interoperable world). To ease the invocation when using an Axis2 client, a helper class is bundled in ode-axis2.jar: <a href="http://ode.apache.org/javadoc/axis2/org/apache/ode/axis2/service/ServiceClientUtil.html">ServiceClientUtil</a>. Usage examples are also available in test classes <a href="http://svn.apache.org/repos/asf/ode/trunk/axis2/src/test/java/org/apache/ode/axis2/management/InstanceManagementTest.java">InstanceManagementTest</a> and <a href="http://svn.apache.org/repos/asf/ode/trunk/axis2/src/test/java/org/apache/ode/axis2/management/ProcessManagementTest.java">ProcessManagementTest</a>. Here is a short example demonstrating the invocation of the <em>listAllProcesses</em> operation:
{code:java}
ServiceClientUtil client = new ServiceClientUtil();
OMElement root = client.buildMessage("listAllProcesses", new String<a href=".html"></a> {}, new String<a href=".html"></a> {});
OMElement result = client.send(msg, "http://localhost:8080/ode/processes/ProcessManagement");</p>
-<div class="codehilite"><pre><span class="n">We</span><span class="s">'re using [XMLBeans](http://xmlbeans.apache.org/) to serialize and deserialize the returned values from/to XML so in the previous example. So if you'</span><span class="n">d</span> <span class="n">like</span> <span class="n">to</span> <span class="n">have</span> <span class="n">objects</span> <span class="n">instead</span> <span class="n">of</span> <span class="n">an</span> <span class="p">[</span><span class="n">Axiom</span><span class="o">|</span><span class="n">http:</span><span class="sr">//</span><span class="n">ws</span><span class="o">.</span><span class="n">apache</span><span class="o">.</span><span class="n">org</span><span class="sr">/commons/</span><span class="n">axiom</span><span class="o">/</span><span class="nb">index</span><span class="o">.</span><span class="n">html</span><span class="p">]</span> <span class="n">structure</span> <span class="n">in</span> <span class="n">the</span>
<span class="n">previous</span> <span class="n">example</span><span class="p">,</span> <span class="n">just</span> <span class="n">add</span> <span class="n">the</span> <span class="n">following</span> <span class="n">lines</span> <span class="n">of</span> <span class="n">code:</span>
+<div class="codehilite"><pre><span class="n">We</span><span class="s">'re using [XMLBeans](http://xmlbeans.apache.org/) to serialize and deserialize the returned values from/to XML so in the previous example. So if you'</span><span class="n">d</span> <span class="n">like</span> <span class="n">to</span> <span class="n">have</span> <span class="n">objects</span> <span class="n">instead</span> <span class="n">of</span> <span class="n">an</span> <span class="p">[</span><span class="n">Axiom</span><span class="p">](</span><span class="n">http:</span><span class="sr">//</span><span class="n">ws</span><span class="o">.</span><span class="n">apache</span><span class="o">.</span><span class="n">org</span><span class="sr">/commons/</span><span class="n">axiom</span><span class="o">/</span><span class="nb">index</span><span class="o">.</span><span class="n">html</span><span class="p">)</span> <span class="n">structure</span> <span class="n">in</span> <span class="n">the</span>
<span class="n">previous</span> <span class="n">example</span><span class="p">,</span> <span class="n">just</span> <span class="n">add</span> <span class="n">the</span> <span class="n">following</span> <span class="n">lines</span> <span class="n">of</span> <span class="n">code:</span>
<span class="p">{</span><span class="n">code:java</span><span class="p">}</span>
<span class="n">ScopeInfoDocument</span> <span class="n">scopeIndoDoc</span> <span class="o">=</span> <span class="n">ScopeInfoDocument</span><span class="o">.</span><span class="n">Factory</span><span class="o">.</span><span class="n">parse</span><span class="p">(</span><span class="n">result</span><span class="o">.</span><span class="n">getXMLStreamReader</span><span class="p">());</span>
</pre></div>
Modified: websites/staging/ode/trunk/content/pxe-deploy-command.html
==============================================================================
--- websites/staging/ode/trunk/content/pxe-deploy-command.html (original)
+++ websites/staging/ode/trunk/content/pxe-deploy-command.html Fri Dec 28 11:21:56 2012
@@ -86,11 +86,11 @@
<p>The <code>pxe-deploy</code> command {excerpt}deploys a system via JMX.{excerpt}</p>
<p><a name="pxe-deployCommand-Synopsis"></a></p>
<h2 id="synopsis">Synopsis</h2>
-<div class="codehilite"><pre><span class="n">pxe</span><span class="o">-</span><span class="n">deploy</span> <span class="p">[</span><span class="o">-</span><span class="sx">q|-v](-vv) -sar file [-jmxurl url] [-domain domain]</span>
-<span class="sx">pxe-deploy -h{noformat}</span>
+<div class="codehilite"><pre><span class="n">pxe</span><span class="o">-</span><span class="n">deploy</span> <span class="p">[</span><span class="o">-</span><span class="sx">q](-v)(-vv) -sar file [-jmxurl url]</span> <span class="p">[</span><span class="o">-</span><span class="n">domain</span> <span class="n">domain</span><span class="p">]</span>
+<span class="n">pxe</span><span class="o">-</span><span class="n">deploy</span> <span class="o">-</span><span class="n">h</span><span class="p">{</span><span class="n">noformat</span><span class="p">}</span>
-<span class="sx">h2. Description</span>
-<span class="sx">The {{pxe-deploy}} command will deploys a system in a running domain via JMX. A [system deployment bundle] for the system can either be at a URL that the target domain can access and read (the {{-url}} argument) or in a local [SAR file|</span><span class="n">SAR</span> <span class="n">File</span><span class="p">]</span> <span class="p">({{</span><span class="o">-</span><span class="n">sar</span><span class="p">}}</span> <span class="n">argument</span><span class="p">)</span><span class="o">.</span>
+<span class="n">h2</span><span class="o">.</span> <span class="n">Description</span>
+<span class="n">The</span> <span class="p">{{</span><span class="n">pxe</span><span class="o">-</span><span class="n">deploy</span><span class="p">}}</span> <span class="n">command</span> <span class="n">will</span> <span class="n">deploys</span> <span class="n">a</span> <span class="nb">system</span> <span class="n">in</span> <span class="n">a</span> <span class="n">running</span> <span class="n">domain</span> <span class="n">via</span> <span class="n">JMX</span><span class="o">.</span> <span class="n">A</span> <span class="p">[</span><span class="nb">system</span> <span class="n">deployment</span> <span class="n">bundle</span><span class="p">]</span> <span class="k">for</span> <span class="n">the</span> <span class="nb">system</span> <span class="n">can</span> <span class="n">either</span> <span class="n">be</span> <span class="n">at</span> <span class="n">a</span> <span class="n">URL</span> <span class="n">that</span> <span class="n">the</span> <span class="n">target</sp
an> <span class="n">domain</span> <span class="n">can</span> <span class="n">access</span> <span class="ow">and</span> <span class="nb">read</span> <span class="p">(</span><span class="n">the</span> <span class="p">{{</span><span class="o">-</span><span class="n">url</span><span class="p">}}</span> <span class="n">argument</span><span class="p">)</span> <span class="ow">or</span> <span class="n">in</span> <span class="n">a</span> <span class="nb">local</span> <span class="p">[</span><span class="n">SAR</span> <span class="n">file</span><span class="o">|</span><span class="n">SAR</span> <span class="n">File</span><span class="p">]</span> <span class="p">({{</span><span class="o">-</span><span class="n">sar</span><span class="p">}}</span> <span class="n">argument</span><span class="p">)</span><span class="o">.</span>
<span class="n">For</span> <span class="n">more</span> <span class="n">information</span> <span class="n">about</span> <span class="n">deployment</span><span class="p">,</span> <span class="n">see</span> <span class="p">[</span><span class="n">System</span> <span class="n">Lifecycle</span><span class="p">]</span><span class="o">.</span>
Modified: websites/staging/ode/trunk/content/receive.html
==============================================================================
--- websites/staging/ode/trunk/content/receive.html (original)
+++ websites/staging/ode/trunk/content/receive.html Fri Dec 28 11:21:56 2012
@@ -106,7 +106,7 @@
</pre></div>
-<p><em>throws</em> <code>[bpel:ambiguousReceive](#ambiguousreceive.html)</code>, <code>[bpel:conflictingReceive](#conflictingReceive)</code>, <code>[bpel:conflictingRequest|#conflictingRequest]</code>, <code>[bpel:correlationViolation|#correlationViolation]</code>, <code>[bpel:invalidVariables|#invalidVariables]</code>, <code>[bpel:uninitializedPartnerRole|#uninitializedPartnerRole]</code>,
+<p><em>throws</em> <code>[bpel:ambiguousReceive](#ambiguousreceive.html)</code>, <code>[bpel:conflictingReceive](#conflictingReceive)</code>, <code>[bpel:conflictingRequest](#conflictingRequest)</code>, <code>[bpel:correlationViolation](#correlationViolation)</code>, <code>[bpel:invalidVariables](#invalidVariables)</code>, <code>[bpel:uninitializedPartnerRole](#uninitializedPartnerRole)</code>,
<code>[bpel:uninitializedVariable](#uninitializedvariable.html)</code></p>
<p><a name="receive-Description"></a></p>
<h3 id="description">Description</h3>
Modified: websites/staging/ode/trunk/content/sendsoap-command.html
==============================================================================
--- websites/staging/ode/trunk/content/sendsoap-command.html (original)
+++ websites/staging/ode/trunk/content/sendsoap-command.html Fri Dec 28 11:21:56 2012
@@ -86,14 +86,14 @@
<p>The <code>sendsoap</code> command {excerpt}uses a lightweight HTTP client to send SOAP messages via POST.{excerpt}</p>
<p><a name="sendsoapCommand-Synopsis"></a></p>
<h2 id="synopsis">Synopsis</h2>
-<div class="codehilite"><pre><span class="n">sendsoap</span> <span class="p">[</span><span class="o">-</span><span class="sx">q|-v](-vv) [-o outfile] url -</span>
-<span class="sx">sendsoap -h{noformat}</span>
+<div class="codehilite"><pre><span class="n">sendsoap</span> <span class="p">[</span><span class="o">-</span><span class="sx">q](-v)(-vv) [-o outfile]</span> <span class="n">url</span> <span class="o">-</span>
+<span class="n">sendsoap</span> <span class="o">-</span><span class="n">h</span><span class="p">{</span><span class="n">noformat</span><span class="p">}</span>
-<span class="sx">h2. Description</span>
-<span class="sx">The {{sendsoap}} command uses a lightweight HTTP client to send SOAP messages via POST using either a file or standard in as the source for the message. The command is useful for testing HTTP endpoints in PXE or external HTTP services that PXE will interact with, as {{sendsoap}} uses the same client as the [HTTP-SOAP Protocol Adapter].</span>
+<span class="n">h2</span><span class="o">.</span> <span class="n">Description</span>
+<span class="n">The</span> <span class="p">{{</span><span class="n">sendsoap</span><span class="p">}}</span> <span class="n">command</span> <span class="n">uses</span> <span class="n">a</span> <span class="n">lightweight</span> <span class="n">HTTP</span> <span class="n">client</span> <span class="n">to</span> <span class="nb">send</span> <span class="n">SOAP</span> <span class="n">messages</span> <span class="n">via</span> <span class="n">POST</span> <span class="n">using</span> <span class="n">either</span> <span class="n">a</span> <span class="n">file</span> <span class="ow">or</span> <span class="n">standard</span> <span class="n">in</span> <span class="n">as</span> <span class="n">the</span> <span class="n">source</span> <span class="k">for</span> <span class="n">the</span> <span class="n">message</span><span class="o">.</span> <span class="n">The</span> <span class="n">command</span> <span class="n">is</span> <span class="n">useful</span> <span class="k">for</span> <s
pan class="n">testing</span> <span class="n">HTTP</span> <span class="n">endpoints</span> <span class="n">in</span> <span class="n">PXE</span> <span class="ow">or</span> <span class="n">external</span> <span class="n">HTTP</span> <span class="n">services</span> <span class="n">that</span> <span class="n">PXE</span> <span class="n">will</span> <span class="n">interact</span> <span class="n">with</span><span class="p">,</span> <span class="n">as</span> <span class="p">{{</span><span class="n">sendsoap</span><span class="p">}}</span> <span class="n">uses</span> <span class="n">the</span> <span class="n">same</span> <span class="n">client</span> <span class="n">as</span> <span class="n">the</span> <span class="p">[</span><span class="n">HTTP</span><span class="o">-</span><span class="n">SOAP</span> <span class="n">Protocol</span> <span class="n">Adapter</span><span class="p">]</span><span class="o">.</span>
-<span class="sx">h2. Options</span>
-<span class="sx">|</span><span class="o">|</span><span class="n">Option</span><span class="o">/</span><span class="n">Argument</span><span class="o">||</span><span class="n">Effect</span><span class="o">||</span>
+<span class="n">h2</span><span class="o">.</span> <span class="n">Options</span>
+<span class="o">||</span><span class="n">Option</span><span class="o">/</span><span class="n">Argument</span><span class="o">||</span><span class="n">Effect</span><span class="o">||</span>
<span class="o">|</span><span class="p">{{</span><span class="n">url</span><span class="p">}}</span><span class="o">|</span><span class="n">the</span> <span class="n">HTTP</span> <span class="n">URL</span> <span class="n">to</span> <span class="n">post</span> <span class="n">the</span> <span class="n">message</span> <span class="n">to</span><span class="o">.|</span>
<span class="o">|</span><span class="p">{{</span><span class="n">file</span><span class="p">}}</span><span class="o">|</span><span class="n">a</span> <span class="n">file</span> <span class="n">containing</span> <span class="n">the</span> <span class="n">message</span> <span class="n">to</span> <span class="n">post</span><span class="o">.|</span>
<span class="o">|</span><span class="p">{{</span><span class="o">-</span><span class="p">}}</span><span class="o">|</span><span class="nb">read</span> <span class="n">the</span> <span class="n">message</span> <span class="n">data</span> <span class="n">from</span> <span class="n">standard</span> <span class="n">in</span> <span class="n">instead</span> <span class="n">of</span> <span class="n">a</span> <span class="n">file</span><span class="o">.|</span>
Modified: websites/staging/ode/trunk/content/wsdl-11-extensions-for-rest.html
==============================================================================
--- websites/staging/ode/trunk/content/wsdl-11-extensions-for-rest.html (original)
+++ websites/staging/ode/trunk/content/wsdl-11-extensions-for-rest.html Fri Dec 28 11:21:56 2012
@@ -139,7 +139,7 @@ Let's assume that such a resource accept
Moreover it's very likely that the resource URI actually describes a set of resources. For instance, the set of posts contained in our imaginary blog: {{http://blog.org/post/\{post_id\}}}.
- HTTP binding offers the [http:operation | http://www.w3.org/TR/wsdl#_http:operation] element to set the path of an operation. While the service address is set in the [http:address](http://www.w3.org/TR/wsdl#_http:address) of the [wsdl:port|http://www.w3.org/TR/wsdl#_ports] element.
+ HTTP binding offers the [http:operation | http://www.w3.org/TR/wsdl#_http:operation] element to set the path of an operation. While the service address is set in the [http:address](http://www.w3.org/TR/wsdl#_http:address) of the [wsdl:port](http://www.w3.org/TR/wsdl#_ports) element.
So one could imagine splitting the URL this way:
{code:xml}
Modified: websites/staging/ode/trunk/content/wsdl-11-http-binding-support.html
==============================================================================
--- websites/staging/ode/trunk/content/wsdl-11-http-binding-support.html (original)
+++ websites/staging/ode/trunk/content/wsdl-11-http-binding-support.html Fri Dec 28 11:21:56 2012
@@ -87,7 +87,7 @@
Actually only the following <a href="http://www.iana.org/assignments/media-types/">MIME types</a> are supported:
1. Media types that represent <a href="http://www.rfc-editor.org/rfc/rfc3023.txt">XML MIME entities</a>. Basically any types matching <code>"text/xml"</code>, <code>"application/xml"</code> and <code>"\*+xml"</code>.
1. Non-XML types will be processed as Text, thus Text Media Types comes de facto but they may have a very limited set of usages.</p>
-<p><a href="http://www.w3.org/TR/wsdl#_mime:multipartRelated">mime:multipartRelated</a>, <a href="http://www.w3.org/TR/wsdl#_mime:soap:body">mime:soap:body</a> and [mime:mimeXml|http://www.w3.org/TR/wsdl#_mime:mimeXml] are not supported.</p>
+<p><a href="http://www.w3.org/TR/wsdl#_mime:multipartRelated">mime:multipartRelated</a>, <a href="http://www.w3.org/TR/wsdl#_mime:soap:body">mime:soap:body</a> and <a href="http://www.w3.org/TR/wsdl#_mime:mimeXml">mime:mimeXml</a> are not supported.</p>
<p>Considering how unsuitable WSDL 1.1 HTTP Binding is for a large majority of services -- especially RESTful services -- a set of extensions is available.
All the details you want to know are <a href="wsdl-1.1-extensions-for-rest.html">here</a>.</p>
</div>