Author: buildbot
Date: Tue Jul 12 21:57:04 2016
New Revision: 992629
Log:
Staging update by buildbot for taverna
Modified:
websites/staging/taverna/trunk/cgi-bin/ (props changed)
websites/staging/taverna/trunk/content/ (props changed)
websites/staging/taverna/trunk/content/documentation/web-service-developers/index.html
Propchange: websites/staging/taverna/trunk/cgi-bin/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Jul 12 21:57:04 2016
@@ -1 +1 @@
-1752351
+1752353
Propchange: websites/staging/taverna/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Jul 12 21:57:04 2016
@@ -1 +1 @@
-1752351
+1752353
Modified:
websites/staging/taverna/trunk/content/documentation/web-service-developers/index.html
==============================================================================
---
websites/staging/taverna/trunk/content/documentation/web-service-developers/index.html
(original)
+++
websites/staging/taverna/trunk/content/documentation/web-service-developers/index.html
Tue Jul 12 21:57:04 2016
@@ -207,7 +207,7 @@ options would yield 4 binding styles, ex
is not WS-I compliant and is <a
href="https://www.ibm.com/developerworks/library/ws-whichwsdl/";>not used</a>.
However, there is an additional binding style that is commonly referred to as
the
document/literal wrapped style. </p>
-<p>Thus, developers have four binding styles to choose from when creating a
WSDL file.</p>
+<p>Thus, developers have 4 binding styles to choose from when creating a WSDL
file.</p>
<ol>
<li>RPC/encoded</li>
<li>RPC/literal</li>
@@ -215,22 +215,22 @@ document/literal wrapped style. </p>
<li>Document/literal wrapped</li>
</ol>
<p>IBM developerWorks has a good description of the <a
href="https://www.ibm.com/developerworks/library/ws-whichwsdl/";>differences
between these styles</a>. </p>
-<p>Although Taverna supports to a fair extent bindings that are
<strong>RPC/encoded</strong> and <strong>RPC/literal</strong>,
+<p>Although Taverna supports to a fair extent bindings that are
<strong>RPC/encoded</strong> or <strong>RPC/literal</strong>,
the preferred binding style is <strong>document/literal wrapped</strong>.
Specifically, the WSDL should have âstyleâ attributes that are set to
âdocument,â "useâ attributes set to âliteral,â
and the parameters should be inside a wrapper.
-This is particularly important when dealing with complex types; for primitive
types, no problems are anticipated.</p>
+This is particularly important when dealing with complex types. For primitive
types, no problems are anticipated.</p>
<h3 id="currently-untested-features">Currently untested features<a
class="headerlink" href="#currently-untested-features" title="Permanent
link">¶</a></h3>
<p>The following are untested and, although not proven to fail, the behaviour
is currently undefined.
For this reason, it is advised to avoid these features.</p>
<ul>
<li>
<p><strong>Multiple WSDL imports.</strong>
- Taverna has only been tested on services that contain no more than one
import of an additional WSDL file.
+ Taverna has only been tested on services that contain <em>no more than
one</em> import of an additional WSDL file.
For WSDLs that import more than one additional WSDL, particularly if that
WSDL has a different service endpoint to the others,
the behaviour of Taverna is currently unclear.
Its expected that it will fail when invoking the Web service.
- <em>This does not affect imports of schemas, which has been thoroughly
tested and works as expected.</em></p>
+ <em>This does not affect import of schemas, which has been thoroughly
tested and works as expected.</em></p>
</li>
<li>
<p><strong>Multiple service endpoints.</strong> For a given WSDL, Taverna
currently only references the first service endpoint.
@@ -239,7 +239,7 @@ For this reason, it is advised to avoid
<li>
<p><strong>Ambiguous type names.</strong>
In the unusual case that an operation requires inputs that contain
identically named types
- that belong to different namespaces, it is expected that Taverna should
not have any problems.
+ belonging to different namespaces, it is expected that Taverna should
not have any problems.
However, because of the unusual nature of this it is untested and therefore
not recommended.</p>
</li>
</ul>
@@ -268,11 +268,11 @@ For this reason, it is advised to avoid
</li>
</ul>
<h2 id="advertise-your-life-sciences-services-with-biocatalogue">Advertise
your Life Sciences services with BioCatalogue<a class="headerlink"
href="#advertise-your-life-sciences-services-with-biocatalogue"
title="Permanent link">¶</a></h2>
-<p>Registering your service in the <a
href="http://www.biocatalogue.org/";>BioCatalogue</a>
- Life Sciences Web Services registry is one of the best ways to make
people aware of your services
+<p>Registering with the <a
href="http://www.biocatalogue.org/";>BioCatalogue</a>
+ Life Sciences Web Services registry is one of the best ways to raise
awareness of your services
and to make them easily discoverable from Taverna and the Web.</p>
<p>With BioCatalogue, service providers can easily register, describe,
advertise and monitor their Web services.
- Users can easily find the right Web service using BioCatalogue's powerful
search and filtering.
+ Users can quickly find the right Web service using BioCatalogue's powerful
search and filtering.
BioCatalogue provides combined information about services from both providers
and community
as it has on-going expert curation as well as social curation by the
community.</p></div>
