commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Harish Krishnaswamy <hkrishnasw...@comcast.net>
Subject Re: [HiveMind] Re: Tapestry exception report incomplete?
Date Thu, 02 Oct 2003 21:17:45 GMT
May be we should classify errors into two types - the ones that can 
proceed and the ones that should crash. Errors like unavailable service 
implementation should probably proceed and those like the parsing errors 
should probably crash?

-Harish

Bill Lear wrote:

>On Thursday, October 2, 2003 at 17:04:20 (-0400) Harish Krishnaswamy writes:
>  
>
>>>...
>>>Why not just toss the thing and let the app catch it?
>>>
>>>      
>>>
>>My understanding is, from a microkernel standpoint, it is not supposed 
>>to crash just because one module or service had a problem, you know like 
>>the containers, they just report the problem and move on. But the 
>>containers have a console or a designated log file that one can take a 
>>look at, but HiveMind does not have either, that will be a problem for 
>>the uninformed, I think.
>>    
>>
>
>Hmm, not sure I agree with this --- if someone mis-configures a
>microkernel, I'd rather have it crash and tell me about it than
>sputter on and die later, pointing me elsewhere by a subsequently
>thrown exception.  I'll have to think and bring pursue discussion on
>the hivemind list.
>
>
>Bill
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>
>  
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message