Re: [proposal] avalon 5 ComponentManager interface

[Stephen McConnell]

I have to confess that I'm way over on Nicola's side here.  The Avlon 
framework CascadingException model enables a consitent approach to 
handling of causal information that is really valuable.

There may be a perfrmace penalty to the following - but for me its well 
and truly justified:

  try
  {
     doSomething()
  }
  catch( Throwable  e )
  {
     throw new CascadingException( "It didn't work.", e );
  }

The impact of the above is that I don't need logging statements in the 
catch because the full information is pased back to the caller. 
Somewhere possibly very high up in the chain, a error is generated in a 
logging file with a complete description based on the collection of 
causal information.  Seconldy, declaration at the interface level that 
an exception is as potential is necessary when your dealing with 
different people components.  If is a custom container handling specific 
components then the scope of the issue is scalled down - but at the 
abstract framework level - exceptions are possible and the more that is 
declared and forced to be managed the better.

Cheers, Steve.


-- 

Stephen J. McConnell

OSM SARL
digital products for a global economy
mailto:[EMAIL PROTECTED]
http://www.osm.net




--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>