Hello, I’ve been looking at the open pull requests in TavMob and attempting to close them. Some I need some guidance on since I’m not sure if they have been merged already. One of them (https://github.com/apache/incubator-taverna-mobile/pull/45) raises some issues about how TavMob would fit into the Taverna 3 ecosystem since it seems to highlight some issues with either the tavern player/portal/server ruby code or with the Tav3 server itself. There are lots of discussions under that pull request but here are the slightly paraphrased highlights (I’m doing this because I read an apache thread somewhere recently about how GitHub discussions don’t always get noticed by the general community):
Ian: “I tried running a couple of t2flow workflows and got a similar error with each from taverna-server-3. @stain I imagine this must be a known bug: Hello-abcd: Caused by: javax.xml.bind.UnmarshalException: unexpected element (uri:"http://ns.taverna.org.uk/2010/xml/server/";, local:"workflow"). Expected elements are <{http://taverna.sf.net/2008/xml/t2flow}abstractConfigBean>,<{}net.sf.taverna.t2.activities.externaltool.ExternalToolActivityConfigurationBean>,<{}net.sf.taverna.t2.activities.interaction.InteractionActivityConfigurationBean>,<{}net.sf.taverna.t2.activities.rest.RESTActivityConfigurationBean>,<{}net.sf.taverna.t2.activities.usecase.UseCaseActivityConfigurationBean>,<{}net.sf.taverna.t2.activities.xpath.XPathActivityConfigurationBean>,<{}net.sf.taverna.t2.component.ComponentActivityConfigurationBean>,<{http://taverna.sf.net/2008/xml/t2flow}workflow> Fetch xkcd: Caused by: javax.xml.bind.UnmarshalException: unexpected element (uri:"http://ns.taverna.org.uk/2010/xml/server/";, local:"workflow"). Expected elements are <{http://taverna.sf.net/2008/xml/t2flow}abstractConfigBean>,<{}net.sf.taverna.t2.activities.externaltool.ExternalToolActivityConfigurationBean>,<{}net.sf.taverna.t2.activities.interaction.InteractionActivityConfigurationBean>,<{}net.sf.taverna.t2.activities.rest.RESTActivityConfigurationBean>,<{}net.sf.taverna.t2.activities.usecase.UseCaseActivityConfigurationBean>,<{}net.sf.taverna.t2.activities.xpath.XPathActivityConfigurationBean>,<{}net.sf.taverna.t2.component.ComponentActivityConfigurationBean>,<{http://taverna.sf.net/2008/xml/t2flow}workflow>” Stian: “Exactly how did you submit how? It seems to do with wrapping XML element or not.. Donal, did something change in the XML requirements for workflow upload in T3? It might be easier to try to do it as a application/vnd.taverna.t2flow+xml upload (Sending binary file as-is) than wrapp it in a <server:workflow> as application/xml.” Ian: “I sent it via taverna-player-portal. I was testing whether they could both be started via docker and play nicely with each other. I haven't tried sending from mobile to portal to server.” “I think the problem might be in https://github.com/myGrid/t2-server-gem/blob/master/lib/t2-server/server.rb#L261 but if you look at the call sequence it seems to be sending as Post with type "application/vnd.taverna.t2flow+xml". I actually managed to recreate the issue by using the t2-server-gem directly in irb. T2Server::Run.create() seems to be where the issue occurs. Doesn't mean it is to blame though. It could be the server that is wrong. Would need to run directly against TavServ3 using curl or similar to find out.” So it looks like there is an issue with running T2 workflows via the portal in T3 server but it is not 100% clear where the fault lies. Sounds like it needs to be raised in Jira if it hasn’t been already. Cheers, Ian Sent from Mail for Windows 10
