Details
-
Bug
-
Status: To Do
-
Minor
-
Resolution: Unresolved
-
None
-
None
Description
When an XML schema changes on the server for a WSDL service, Taverna will recognize this on loading the workflow. (Although one might need to restart Taverna if the WSDL has been encountered before the changes were applied).
However, the XML input and output splitters in a workflow have their XML schema bits hardcoded, and are not automatically updated. The user is currently required to remove such splitters, then add & link up the splitters again, in order for the splitters to use the updated schemas.
This is mainly relevant for while developing a web service, but also affects workflows where the service has change, as a minimum Taverna should try to detect this change and let the user know.
Planned work:
1. Check that work on replacing a service covers this.
Planned testing:
1. Create a WSDL service and then alter its xsd
2. Check that the change is detected
3. Check that users are able to fix the problem.
Attachments
Issue Links
- is cloned by
-
TAVERNA-344 Highlight when a service definition has changed
- To Do
- relates to
-
TAVERNA-335 Need ability to update/replace service
- To Do