Mark Wilkinson wrote: > Cheers Alan! > > One last question - I think it's directed as Stian (Eddie tells me that he > has already reported the bug).
Yes it's in as T2-602. > There's something about the way > apostrophes are escaped in port names that is preventing some of our > workflows from running in T2. This is unfortunate because the main > workflow that we use for our training courses is one of those affected by > this bug... and the training course is only a few weeks away. It shouldn't prevent the workflows running (as far as I know). It does affect the capture and display of provenance information. The provenance database doesn't like the port names. > Is there an ETA on this bug-fix? It sadly hasn't made it into the beta 2 release. We had a discussion about where to fix the problem. At the moment Taverna checks the validity of portnames only in the UI. Hence an activity can (via the API) put in names that you couldn't enter when creating, say, a workflow port. The correct place to catch it would probably be in the code called by the API and then throw an exception, or possibly to distinguish between port ids and port (display) names. A temporary fix would be to either get the Moby plugin to normalise the port names, or to get the provenance database to normalise them for the database. It can perhaps be done as an update to 2.1 beta 2. > M Alan ------------------------------------------------------------------------------ _______________________________________________ taverna-hackers mailing list [email protected] Web site: http://www.taverna.org.uk Mailing lists: http://www.taverna.org.uk/taverna-mailing-lists/ Developers Guide: http://www.mygrid.org.uk/tools/developer-information
