[Fortress/Event] catching runtime exceptions

[Filip Defoort <fi...@cirquedigital.com>]

Hi,

I'm looking for a way to trap the exceptions that my components 
generate... Fortress
by default 'just' displays the exceptions to stdout. In my case, as soon 
as any component
generates any exception, this is a serious problem and I need to take 
some measures..
I've been digging around a bit in the excalibur event packages and found 
two
possible places where I need to make some changes -- CommandManager and
ThreadManager..

Anybody any idea where exactly I need to make a change // any 
suggestions for
a listener interface of some sort that we can put there so that this can 
be reused
later ?

Thanks a lot,
- Filip



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org

Re: [Fortress/Event] catching runtime exceptions

[Anton Tagunov <at...@mail.cnt.ru>]

Hello Filip!

FD> I'm looking for a way to trap the exceptions that my components
FD> generate... Fortress
FD> by default 'just' displays the exceptions to stdout. In my case, as soon 
FD> as any component
FD> generates any exception, this is a serious problem and I need to take 
FD> some measures..

I understand that you want to get e-mail notifications or something
alike? That is very much possible. To achive this you should make
use of logger in your components, maybe with .error() in case of
the most serious errors you want notification about. Then you should
learn to configure your logging system.

I'm not good at this at all (yet to study :-) but I
understand that you may configure either
Logkit or Log4j. I beleive both of them have facilities for
sending e-mail notification.
Clue: if you do not know where to start try it with Logkit.

The logging system in Fortress is configured via the

FortressConfig.setLoggerManagerConfiguration(
    path-to-logkit-configuration-file)

Fortress contains the following sample

    src/test/o/a/a/fortress/test/data/test1.xconf

Unoftunantly this all the help that I personally can offer you,
but maybe others can.

Try to refer to the documentation on the
http://avalon.apache.org
site and to documentation on logkit/log4j

I beleive you may also find experienced Avalon
users ready to help you at users@avalon.apache.org

- Anton


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org