You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@taverna.apache.org by bu...@apache.org on 2015/02/24 15:45:22 UTC
svn commit: r941332 - in /websites/staging/taverna/trunk: cgi-bin/ content/
content/documentation/web-service-developers/index.html
Author: buildbot
Date: Tue Feb 24 14:45:22 2015
New Revision: 941332
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 Feb 24 14:45:22 2015
@@ -1 +1 @@
-1661926
+1661968
Propchange: websites/staging/taverna/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Feb 24 14:45:22 2015
@@ -1 +1 @@
-1661926
+1661968
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 Feb 24 14:45:22 2015
@@ -4,7 +4,7 @@
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1">
- <title>Apache Taverna - </title>
+ <title>Apache Taverna - Web service developers</title>
<meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
<meta property="og:image" content="/img/taverna-logo-145x134.png" />
@@ -31,7 +31,7 @@
"@context" : "http://schema.org",
"@type" : ["CreativeWork"],
"@id": "",
- "name" : "",
+ "name" : "Web service developers",
"publisher" : {
"@type" : "Organization",
"url" : "http://www.apache.org/",
@@ -163,7 +163,7 @@
<div id="page" class="container">
- <h1></h1>
+ <h1>Web service developers</h1>
<div class="alert alert-info" role="alert"><p><span class="glyphicon glyphicon-info-sign" aria-hidden="true"></span>
Taverna is transitioning to the Apache Incubator.
@@ -172,7 +172,75 @@ Instead it shows <a class="alert-link" h
</div>
- <div id="content"><p>TO DO</p></div>
+ <div id="content"><p>Taverna aims to support Web services that are
+ <a href="http://www.ws-i.org/Profiles/BasicProfile-1.1-2004-08-24.html">WS-I</a> (Web Services Interoparability) compliant,
+ but this is a long-term goal and currently there are a few nuances.
+However, it should be possible to create Web services that are compatible with Taverna if you follow certain guidelines.</p>
+<h2 id="wsdl-web-service-description-language-style-web-services">WSDL (Web Service Description Language) style Web services</h2>
+<p><a href="/documentation/glossary#wsdl">WSDL</a> binding describes how the Web service is bound to a messaging protocol;
+ particularly the SOAP messaging protocol.
+A WSDL SOAP binding can be either a <strong>Remote Procedure Call (RPC)</strong> style binding or a <strong>document</strong> style binding.
+A SOAP binding can also have an <strong>encoded</strong> use or a <strong>literal</strong> use.
+This gives you four style/use models:</p>
+<ol>
+<li>RPC/encoded</li>
+<li>RPC/literal</li>
+<li>Document/encoded</li>
+<li>Document/literal</li>
+</ol>
+<p>There is also a fifth binding style that is commonly referred to as the document/literal wrapped.
+Thus, developers have five binding styles to choose from when creating a WSDL file.</p>
+<p>A good description of the differences between these styles can be found
+ <a href="http://www-128.ibm.com/developerworks/webservices/library/ws-whichwsdl/">here</a>.</p>
+<p>Although Taverna supports bindings that are <strong>RPC/encoded</strong> and <strong>RPC/literal</strong> to a fair extent,
+ the preferred binding style is <strong>document/literal wrapped</strong>,
+ i.e. the WSDL should have âstyleâ attributes that are set to âdocumentâ and âuseâ attributes set to âliteralâ.
+This is particularly the case when dealing with complex types; for primitive types no problems are anticipated.</p>
+<h3 id="currently-un-tested">Currently un-tested</h3>
+<p>The following are untested, and although not proven to fail the behaviour is currently undefined.
+For this reason it is advised that these features are avoided.</p>
+<ul>
+<li>Multiple WSDL imports.
+ Taverna has only been tested on services that contain either no, or only one 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.
+ This does not affect imports of schemas.
+ This has been thoroughly tested and works as expected.</li>
+<li>Multiple service endpoints. For a given WSDL Taverna currently only references the first service endpoint.
+ If more than one exists then operations belonging to the second endpoint are expected to fail.</li>
+<li>Ambiguous type names.
+ 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.
+ However, because of the unusual nature of this it is untested and therefore not recommended.</li>
+</ul>
+<h3 id="currently-known-to-fail">Currently known to fail</h3>
+<p>The following are situations that are known to fail in Taverna.</p>
+<ul>
+<li>Cyclic references.
+ When processing the result of invoking an operation, Taverna resolves the XML into a single document.
+ If the response contains cyclic references, this is detected and an error occurs (to prevent an infinitely long document!).
+ For this reason cyclic references should be avoided.
+ (Taverna will, however,
+ work with such an operation as long as the cyclic reference is not contained within the response data structure).</li>
+<li>Overloaded operations. Within the UI,
+ Taverna only distinguishes between operations, for a given service, by name.
+ The operation signature is not used to distinguish between operations of the same name.
+ For this simple reason, Taverna does not support overloaded operations.</li>
+<li>anyType.
+ Although Taverna can invoke a service that deals with the anyType type,
+ the XML splitting mechanism cannot work since there is no information about the data structure required or received.
+ Such services can only be used by providing and/or manipulating the XML directly.</li>
+</ul>
+<h2 id="advertise-your-services-with-biocatalogue">Advertise your services with BioCatalogue</h2>
+<p>If your services are in the Life Sciences domain,
+ one of the best ways to make people aware of your services and make them easily discoverable from Taverna and
+ the Web is to register and describe them in <a href="http://www.biocatalogue.org/">BioCatalogue</a>
+ Life Sciences Web Services registry.</p></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.
+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>
</div>