A lot of the built-in actors throw exceptions in certain situations. Is there some way to gracefully catch these exceptions, particularly when we are running kepler workflows from the command line (i.e. without the GUI)? For example, the XPath Processor throws an exception if it doesn't find the path specified, but this might not always really be an error in an actual workflow. Is there any way we could automatically recover from this error and continue execution?
More generally, is there any way to externally monitor Kepler's execution status? Thanks. Christine -------------------------------- Dr. Christine Smit [email protected]<mailto:[email protected]> +1-301-614-5752 NASA Goddard, Building 32, N126-12 Code 610.2
_______________________________________________ Kepler-users mailing list [email protected] http://lists.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-users
