Hi Martin,
 There has been a proposal of mine which occurred after a discussion
with Nina on a formal way to report errors and exceptional conditions
which resembles the way Java handles the exceptions. The main idea
behind it is that when a service acts as a proxy to another service and
the second returns an error, according to RFC this should be an error
with code 502. But this is not very specific for another machine to
understand the reason the error happened; that is services are masking
the errors under 502. So, it is better if we have a formal way to
communicate the error details in the response body. If everyone agrees
we can use this convention (see also
http://opentox.org/dev/apis/api-1.1/Error%20Reports ).

Best Regards,
Pantelis

On Fri, 2010-05-07 at 14:43 +0200, Martin Guetlein wrote:
> Hello All,
> 
> do we have agreed on how to report task errors?
> 
> I noticed that Ambit and Ntua services return an Error Report object
> alongside with the Task object (see attachment).
> 
> Could we add a reference from the Task object to the Error object (maybe in
> Task.description?)?
> 
> Best regards,
> 
> Martin
> 
> _______________________________________________
> Development mailing list
> Development at opentox.org
> http://www.opentox.org/mailman/listinfo/development