I'll look into it more.  I was assuming that it
doesn't take care of the exception properly because
the log gets blown up with the stack trace.  Perhaps
the specific java method had the error.  Thanks.

--- David E Jones <[EMAIL PROTECTED]>
wrote:


> In general this is a service environment and not a
> "Java" environment  
> and so exceptions aren't all that helpful. Passing
> messages around is  
> the way to go, and we do have various things like a
> message wrapper  
> object so you can identify where the error happened,
> and the message  
> Map that Jacopo mentioned so you can give each
> message a name/key.
> 
> What I'm wondering about your proposal is how it is
> different and  
> better than existing methods of error handling and
> message passing,  
> including the two I mentioned above.
> 
> -David
> 
> 

Reply via email to