[TAVERNA-335] Need ability to update/replace service

• Type: Bug
• Status: To Do
• Priority: Major
• Resolution: Unresolved
• Component/s: Taverna Workbench
• Assignee: Unassigned
• Reporter: Stian Soiland-Reyes
• Created: 18/Mar/10 16:32
• Updated: 28/Apr/15 11:42

Description

If a service is offline or no longer matches its definition, users need to be able to change the called service. This could be done by altering its details, for example, its operation name or its endpoint.

More complex replacement could be done by dragging over the replacement service. This would open up a dialog similar to a workflow where the ports of the old description (analogous to the workflow ports) can be linked to the ports of the replacement service. When this replacement dialog was closed, the names of the ports would be changed to that of the replacement service.

Users do not want to have to recreate all the links.

Planned work:

1. For each service type, where applicable, allow endpoint etc. alteration
2. Consider the complex cases of WSDLs with splitters, compond Moby objects
3. Create a nested-workflow like re-binding dialog

Issue Links

• is related to: TAVERNA-130 XML splitters not updated when XML schema changes on server
• relates to: TAVERNA-344 Highlight when a service definition has changed