[kepler-dev] Nondeterministic merge in PN domain

[Bertram Ludaescher]

I think we can even distinguish a whole bunch of different failures (a
failure ontology is needed! :)

E.g. we migh havefailures/exceptions:
- at the Java level
- when invoking a remote (non-responsive) service
- when a service tells us "does not compute"
etc.

different techniques (retry, fail-over, tag-and-forget, etc.) will
probably be useful for different types of errors and different
application scenarios .. 

Bertram



>>> On Wed, 19 Jul 2006 09:22:53 -0700
>>> "Edward A. Lee" <eal at eecs.berkeley.edu> wrote: 
EAL> 
EAL> Pertinent to this, Haiyang Zheng just enriched the exception handling
EAL> capabilities in Ptolemy II...  Currently, if you create an actor
EAL> that implements the ExceptionHandler interface and put it into a model,
EAL> then any exception that occurs when the model is executes gets delegated
EAL> to that actor.  The first such actor is a test actor that can be used
EAL> to make regression tests that ensure that an exception is thrown.
EAL> 
EAL> Edward
EAL> 
EAL> At 04:46 PM 7/18/2006, Mladen Vouk wrote:
>> Hi everyone,
>> 
>> Do we, somewhere on the Kepler/Ptolemy websites, or in one of our papers,
>> have a relatively comprehensive description of current exception handling
>> capabilites of Kepler
>> (e.g.,  somewhat more elaborate and perhaps up to date than is given in)
>> 
>> http://www.gridbus.org/~raj/papers/workflow-sigmod05.pdf
>> 
>> ?
>> 
>> Thanks
>> 
>> Mladen
>> 
>> 
>> _______________________________________________
>> Kepler-dev mailing list
>> Kepler-dev at ecoinformatics.org
>> http://mercury.nceas.ucsb.edu/ecoinformatics/mailman/listinfo/kepler-dev
EAL> 
EAL> ------------
EAL> Edward A. Lee
EAL> Professor, Chair of EECS
EAL> 231 Cory Hall, UC Berkeley, Berkeley, CA 94720-1770
EAL> phone: 510-642-0253 or 510-642-0455, fax: 510-642-2845
EAL> eal at eecs.Berkeley.EDU, http://ptolemy.eecs.berkeley.edu/~eal