Forwarding this from a discussion on taverna-users a couple of weeks ago...
Did anyone have any ideas in the end on whether this problem was easily fixable? I'd like to be able to distribute example Taverna workflows for our services, but this makes it impossible, for some of them at least. Thanks, Andrew. 2009/5/19 Andrew Clegg <[email protected]>: > 2009/5/19 Stian Soiland-Reyes <[email protected]>: >> 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"> > > Yep, that's what I had in mind... > >> 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? > > Err... Not an expert in rpc/encoded, but when I remove the name > attribute, Eclipse says: > > cvc-complex-type.4: Attribute 'name' must appear on element 'wsdl:service'. > > I *think* this is an XSD validation error so this would be true in > rpc/encoded too. > >> 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?): > ... >> 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..) > > Well, everything in the WSDL is in the targetNamespace defined in the > root element, right? > > I think the correct way to identify a service is like: > > {http://funcnet.eu/FuncNet_1_0/}CodaCathService > > i.e. {namespace-uri}ServiceName > >> 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 think we would need operation name -- a port type can have multiple > operations -- I think this is pretty common actually, e.g. in > submit/monitor/retrieve services. > > But I disagree about using the WSDL for the reasons in the last mail :-) > > {namespace-uri}ServiceName -> PortType -> operation ?? > >> I suggest moving this to taverna-hackers - are you on that list, Andrew..? > > Err, I am now, feel free to reply there instead... > > Andrew. > > -- > :: http://biotext.org.uk/ :: > -- :: http://biotext.org.uk/ :: ------------------------------------------------------------------------------ OpenSolaris 2009.06 is a cutting edge operating system for enterprises looking to deploy the next generation of Solaris that includes the latest innovations from Sun and the OpenSource community. Download a copy and enjoy capabilities such as Networking, Storage and Virtualization. Go to: http://p.sf.net/sfu/opensolaris-get _______________________________________________ taverna-hackers mailing list [email protected] Web site: http://www.taverna.org.uk Mailing lists: http://www.taverna.org.uk/taverna-mailing-lists/ Developers Guide: http://www.mygrid.org.uk/tools/developer-information
