On Fri, Jun 5, 2009 at 12:08, Andrew Clegg <[email protected]> wrote:
> That isn't the only case that could cause problems though, just the > most severe. If I remember correctly (at home without a Taverna > installation) there's no way to tell from the UI which operation > relates to which service, so even if they do have different names, > users will only be able to tell what service they're dealing with by > viewing the WSDL source. So any WSDL with multiple services will be a > confusing experience for users, even if the ops are named differently. Good point - so representation-wise you would also need some work for the workflow designer to select the right one - like deeper folders within the WSDL in the Service Panel, and showing more information such as descriptions from the WSDL file. We still have not treated either multiple bindings for the same operation/action - which in theory you could also do in the WSDL - those would then be between equivalent service endpoints - so Taverna should probably try each of them in order on failure - but keep a record of which one was 'really' used. -- Stian Soiland-Reyes, myGrid team School of Computer Science The University of Manchester ------------------------------------------------------------------------------ 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
