On Tue, May 19, 2009 at 10:07, Alan Williams <[email protected]> wrote:
>>> construct that doesn't really describe what's in it. The URI of each
>>> service in the WSDL would be a better discriminator, right?
>> Sorry, I meant "the qualified name of each service in the WSDL" --
>> i.e. namespace + servicename.
> I agree. The namespace + servicename + operation would seem to be
> better. I will ask Stuart Owen (our WSDL expert) what he thinks.
What is 'servicename'? Do you mean like in the binding?
<wsdl:service name="HippiService">
<wsdl:port binding="tns:HippiBinding" name="HippiPort">
<soap:address
location="http://funcnet.eu/BioMiner-war/services/HippiService"; />
<http-conf:client ReceiveTimeout="0" />
<http-conf:client ConnectionTimeout="0" />
</wsdl:port>
</wsdl:service>
I'll let Stuart comment, I guess this would also differentiate between
different service bindings in the same file - but is a wsdl:service
required to have a name? Even in old-style RPC/encoded?
Also a <wsdl:service> can have *multiple* ports inside, but they are
meant to be somewhat equivalent pr port type (perhaps this could be
used for some redundancy?):
From http://www.w3.org/TR/wsdl#_services
# If a service has several ports that share a port type, but employ
different bindings or addresses, the ports are alternatives. Each port
provides semantically equivalent behavior (within the transport and
message format limitations imposed by each binding). This allows a
consumer of a WSDL document to choose particular port(s) to
communicate with based on some criteria (protocol, distance, etc.).
# By examining it's ports, we can determine a service's port types.
This allows a consumer of a WSDL document to determine if it wishes to
communicate to a particular service based whether or not it supports
several port types. This is useful if there is some implied
relationship between the operations of the port types, and that the
entire set of port types must be present in order to accomplish a
particular task.
My favourite would be to do it on the port type and operation name - I
don't think they would need to be fully qualified as they can't have
namespace prefixes anyway within a WSDL. (again I'm not sure about
that..)
To do this 100% - would we need to do wsdl URL, service name and port
type name - or do we then also need operation name?
I suggest moving this to taverna-hackers - are you on that list, Andrew..?
--
Stian Soiland-Reyes, myGrid team
School of Computer Science
The University of Manchester
------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables
unlimited royalty-free distribution of the report engine
for externally facing server and web deployment.
http://p.sf.net/sfu/businessobjects
_______________________________________________
taverna-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/taverna-users
Documentation: http://www.mygrid.org.uk/usermanual1.7/
FAQ: http://www.mygrid.org.uk/wiki/Mygrid/TavernaFaq
Biological Services: http://www.mygrid.org.uk/wiki/Mygrid/BiologicalWebServices
