On Tue, May 19, 2009 at 07:18, Andrew Clegg <[email protected]> wrote:
> describes four distinct services, but in Taverna they're only referred > to by the WSDL and the operation. In this case the problem is > particularly emphasized because each of the services -- by design -- > supports the *same* operation with the *same* parameters. (They are > different prediction algorithms which each expose the same interface.) I would say that if they are different prediction algorithms, they are different operations. :-) (unless they end up with the same answer..?) > So, in Taverna I get four operations called 'ScorePairwiseRelations', > with no way to tell which of the four services in the WSDL they're > referring to. This seems to be a bug, it is right that we only identify a WSDL operation by the URL of the WSDL and the operation name. This means that the first portType with a matching operation will be selected. We can argue if it's good design or not to have several port types with the same operation name inside, as I guess this could be troublesome for many other clients as well. I have however noted this as a bug, because this might not be the only service out there with several port types. > Is this intentional? If so, it seems a bit strange -- multiple-service > WSDLs are schema-valid, and compliant with the WS-I interop > guidelines. And the URL of a WSDL file is surely an entirely arbitrary > construct that doesn't really describe what's in it. The URI of each > service in the WSDL would be a better discriminator, right? No, the binding address would be much worse as a discriminator, as there could be several bindings to the same location - that is precisely how many Document/literal services works, where the binding address is the same, but the operations are separated simply on what is the top-level message element type/name. Also the binding address is updatable, so that the WSDL can point to a new endpoint without affecting the workflow. (I know this is very seldomly done, though) I think a good discriminator would be wsdl location, port type and operation name. I've forwarded this also to the biocatalogue team as BioCatalogue seem to fail to parse http://funcnet.eu/soap/CodaCath.wsdl I've noted this as a new Taverna bug: http://www.mygrid.org.uk/dev/issues/browse/T2-587 > Also, an unrelated issue -- my preferences window has two identical > 'data storage' pages. This is on Java 1.6 u10 on Centos 5. This is a known bug, but it should not be harmful as both pages update each other. http://www.mygrid.org.uk/dev/issues/browse/T2-489 -- 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
