Hello, This may be a silly question but just to be sure.
I came across an old mailing list post while searching for info about whether it is possible to parallelize the workflow execution somehow, preferably internally (parallelize the different activities, vs different execution engines)(*). In the post there is this snippit(**): >Taverna workflows don't specify jobs that >are to be done and executing a Taverna workflow does not typically do >much local processing. Taverna works in a world of web services and >other remote resources - so when it comes down to 'executing a >workflow on the grid' there are really two things one are talking >about... I am aware of Tavernas web-service bias, but assumed it would also work fine for long running processes (think many hours). This snippit made me wonder if certain design choices or roadmap plans would make Taverna less ideal for such long running workflows? Cheers Dirk (*) does not really seem to be possible without a lot of hacking, maybe osgi will help? (**) from http://www.mail-archive.com/[email protected]/msg00475.html -----Original Message----- From: Marta Villegas [mailto:[email protected]] Sent: 23 September 2010 14:41 To: [email protected] Subject: [Taverna-users] problems with xml-splitter (and Hi, I'm having problems with xml splitter using a Soaplab wsdl. The wsdl is at http://gilmere.upf.edu:9910/soaplab2/typed/services/panacea.get_p?wsdl. We have been testing with Soaplab 2.2 and 2.3. In the first case, the runAndWaitFor message is described as follows: <message name="runAndWaitForResponse"> <xs:element name="runAndWaitForResponse" type="tns:appResults"/> whereas in the 2.3 version the same message is described as: <message name="runAndWaitForResponse"> <xs:element name="runAndWaitForResponse" type="tns:RunAndWaitForResponse"/> As tou can see, this runAndWaitForResponse type is just a wrapper for the former appResults: <xs:complexType name="RunAndWaitForResponse"> <xs:complexContent> <xs:extension base="tns:appResults"/> </xs:complexContent> </xs:complexType> The thing is that when this wsdl, the xml splitter in Taverna does not work as the splitter processor has no en totes les versions de Taverna: - soaplab2: el "run and wait for" té output (parameters) però quan fas un xmlsplit aquest té input però no otputs - soaplab22: el "run and wait for" té output (runAndWaitForResponse) i quan fas un xmlsplit tot va ok (genera input i outputs) la diferència entre el el soaplab2 i el 22 pel que fa al response és que <xs:element name="runAndWaitForResponse" type="tns:appResults"/> v 22 <xs:element name="runAndWaitForResponse" type="tns:RunAndWaitForResponse"/> v 2 és a dir sempre que tenim una restriction del tipus: <xs:complexType name="RunAndWaitForResponse"> <xs:complexContent> <xs:extension base="tns:appResults"/> </xs:complexContent> </xs:complexType> la cosa no funciona. Als nostres web services tenim extensions : <complexType name="TokenizerResponseType"> <complexContent> <extension base="ns:ResponseType"> <sequence> <element name="TokenizedText" type="ns:TextType"/> </sequence> </extension> </complexContent> </complexType> la diferència és que en el nostre cas afegin coses quan fem un extension i al soaplab no (???) -- Marta Villegas [email protected] ------------------------------------------------------------------------------ Nokia and AT&T present the 2010 Calling All Innovators-North America contest Create new apps & games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev _______________________________________________ taverna-users mailing list [email protected] [email protected] Web site: http://www.taverna.org.uk Mailing lists: http://www.taverna.org.uk/about/contact-us/
