we wrap the ConfigurationException (or a ServiceException for that case) into something like
o.a.a.fotress.ActivationException extends CascadingException
{
ActivationExcption( String id, Throwable t ) { super( id, t ); }
}
Goes without saying that for this exception we will produce no trace either.
So this is what the user will get in log:
ActivationException: 'cool-component' caused by
ConfigurationException: badly broken config: file:/D:/conf/super.xconf:27
I like this.
As for stack trace suppression, I believe that should be done at the logger level, rather than having 'no stack traces' be hardcoded.
-pete
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
