Difference between revisions of "Web services package"
Jump to navigation
Jump to search
| Line 6: | Line 6: | ||
*** This page on stackoverflow can also be useful: [http://stackoverflow.com/questions/206154/whats-the-best-soap-client-library-for-python-and-where-is-the-documentation-fo What's the best SOAP client library for Python, and where is the documentation for it?] | *** This page on stackoverflow can also be useful: [http://stackoverflow.com/questions/206154/whats-the-best-soap-client-library-for-python-and-where-is-the-documentation-fo What's the best SOAP client library for Python, and where is the documentation for it?] | ||
*** Here's how Taverna handles Web Services: | *** Here's how Taverna handles Web Services: | ||
**** http://www.taverna.org.uk/introduction/services-in-taverna/ | **** http://www.taverna.org.uk/introduction/services-in-taverna/ the model is that any "plain" SOAP service can be used immediately, given the URL of its WSDL specification, while some special collections like caGrid, Biomoby and other services need a Taverna plugin to be used, due to their specific requirements (regarding security, for example). | ||
the model is that any "plain" SOAP service can be used immediately, given the URL of its WSDL specification, while some special collections like caGrid, Biomoby and other services need a Taverna plugin to be used, due to their specific requirements (regarding security, for example). | |||
**** They use Axis 1 to parse WSDLs and call web services, but built an [http://taverna.googlecode.com/svn/taverna/utils/net.sf.taverna.wsdl-generic/trunk/ overlay on top of Axis1 to do higher-level support], for instance caching of XSDs and header support. | **** They use Axis 1 to parse WSDLs and call web services, but built an [http://taverna.googlecode.com/svn/taverna/utils/net.sf.taverna.wsdl-generic/trunk/ overlay on top of Axis1 to do higher-level support], for instance caching of XSDs and header support. | ||
**** REST support is currently under development with an alpha due out in September. | **** REST support is currently under development with an alpha due out in September. | ||
Revision as of 18:35, 13 October 2010
- Tommy investigate what a good web service library that can be integrated with VisTrails
- Emanuele's pointers:
- It is important to have in mind that we need to create Modules for methods and types on the fly. ZSI provided a way to generate class stubs for all methods and types in a wsdl file and VisTrails used those to create the Modules. I believe the other libraries can't do that so we might have to do that ourselves.
- Potential library: SUDS (https://fedorahosted.org/suds/)
- Tommy: It looks like a good alternative.
- This page on stackoverflow can also be useful: What's the best SOAP client library for Python, and where is the documentation for it?
- Here's how Taverna handles Web Services:
- http://www.taverna.org.uk/introduction/services-in-taverna/ the model is that any "plain" SOAP service can be used immediately, given the URL of its WSDL specification, while some special collections like caGrid, Biomoby and other services need a Taverna plugin to be used, due to their specific requirements (regarding security, for example).
- They use Axis 1 to parse WSDLs and call web services, but built an overlay on top of Axis1 to do higher-level support, for instance caching of XSDs and header support.
- REST support is currently under development with an alpha due out in September.
- Emanuele's pointers: