Haschemi [hasch...@informatik.hu-berlin.de]
SENT: Saturday, March 12, 2011 11:33 AM
TO: OSGi Developer Mail List
SUBJECT: Re: [osgi-dev] exception aggregation for error reporting?
Hi Michael,
although you mentioned that you don't want to use AOP, it seems to be
the best way for me. And since
Creating a ThreadGroup is one thing, getting rid of it is quite another -
you have to call ThreadGroup.destroy() from outside the ThreadGroup after
all the member threads have terminated. Otherwise you have a classloader
leak:
Well, this was the central tenet of my blog. Never catch exceptions when you
cannot do something really useful with them (like 99% of the cases) and let
them bubble up to the highest level. At the highest level you usually have a
clear way to report back what went wrong. E.g. before you call a
Hi Michael,
although you mentioned that you don't want to use AOP, it seems to be the best
way for me. And since OSGi has the clear Lifecycle, you could define your
pointcuts based on the OSGi API methods. You can further put all your
Java-Threads in a ThreadGroup, and overwrite
I am not sure I understand the question, in Java the exceptions are thrown to
callers so a good design allows the top level to centralize handling exceptions
(see my blog about Exception Hygiene). However, this is kind of orthogonal to
OSGi.
Kind regards,
Peter Kriens
On 11 mrt 2011,
