I had a similar experience--I tried to write a workflow that started up another workflow by running executeworkflow.sh as a shell command, only to have the first workflow immediately stop running. (This is on Mac OS X 10.6 with Taverna 1.7.) I didn't note any error messages unfortunately.
On 26 Nov 2009, at 6:41 AM, [email protected] wrote: > Date: Sun, 22 Nov 2009 11:01:34 -0500 (EST) > From: [email protected] > Subject: [Taverna-users] Using the executeworkflow.sh > > Hi All: > > I have a taverna workflow that contains several processors where each process > execute a .exe program. The workflow takes two inputs. If I call the > executeworkflow.sh to execute the workflow with the two inputs, it work fine. > Once it finishes executing, I call it again after changing the content of > the inputs and it will work fine. > > The problem is: > If i call the executeworkflow.sh to execute the workflow and before it > finishes executing i call it again to execute the second workflow, it will > not work. Kevin Crowston Syracuse University Phone: +1 (315) 464-0272 School of Information Studies Fax: +1 (866) 265-7407 348 Hinds Hall Web: http://crowston.syr.edu/ Syracuse, NY 13244-4100 USA ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ taverna-users mailing list [email protected] [email protected] Web site: http://www.taverna.org.uk Mailing lists: http://www.taverna.org.uk/taverna-mailing-lists/
