Details
-
Bug
-
Status: To Do
-
Major
-
Resolution: Unresolved
-
None
-
None
Description
A user tried to import a WSDL description that was Soap 1.2 and did not include the Soap 1.1 equivalent. Taverna 2.1 (and 1.7) did not find any problems in the WSDL but did not recognise any WSDL operations. The WSDL description is attached.
Solution:
We're not going to add proper SOAP 1.2 support now. However, one quick fix that seems to work at least in this case is simply to do a substitution of the namespace to use the 1.1 namespace instead. This could be done by some detection/rewrite magic in the beginning of the WSDL parsing. XSD parsing should not be affected.
Testing:
Load attached WSDL in 2.1.0 where it should fail, and in 2.1.2 where it should work.
Attachments
Attachments
Issue Links
- is related to
-
TAVERNA-320 WSDL 1.1 and 2 should be supported
- To Do