This is one more level of abstraction rather than using switch and join actors. I am not sure it contributes to correct workflow model design. Same design can be implemented by putting the latters into a composite actor.
Ustun. On Wed, Dec 9, 2009 at 2:07 PM, Bertram Ludaescher <ludaesch at ucdavis.edu> wrote: > One more note: Dan Crawl from SDSC has developed a mechanism to define > "alternate workflow routes" as a means to aid workflow design and increase > fault-tolerance. > He might be able to point you to additional ways to do error handling.. > > Bertram > > -- > Bertram Lud?scher > Professor of Computer Science > Dept of Computer Science & Genome Center > University of California, Davis > ludaesch at ucdavis.edu / www.daks.ucdavis.edu > Ph: +1-530-554-1800 > > On Wed, Dec 9, 2009 at 8:22 AM, Barbara Lerner <blerner at mtholyoke.edu> > wrote: >> >> Hi, >> >> ?I am new to Kepler and I am trying to understand how exception handling >> is done in Kepler. ?I see two actors: ?Throw Exception and Throw Model >> Error. ?From the documentation, it seems that using Throw Model Error would >> allow one to catch the error elsewhere in the workflow, but I don't see any >> discussion of how I would do that. ?Can someone explain this or point me to >> the documentation that does? >> >> Thanks, >> ?Barbara >> >> ------------------ >> >> Barbara Lerner ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?"Power to >> the peaceful" >> Associate Professor ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?-- >> Michael Franti >> Computer Science Dept. >> Mt. Holyoke College >> >> >> >> >> _______________________________________________ >> Kepler-users mailing list >> Kepler-users at kepler-project.org >> http://mercury.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-users > > > _______________________________________________ > Kepler-users mailing list > Kepler-users at kepler-project.org > http://mercury.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-users > >
