Niclas Hedhman wrote:
Gang,
here is an interesting problem;
If an Exception occurs during activate(), all services that has
already been started will be passivated then the exception bubbles to
the surface.
But, if an Exception occurs during passivate(), the exception bubbles
to the surface immediately and all services are not passivated, which
can lead to resources hanging around.
I suggest that passivate() will try to shut down all services, and if
more than one exception happens during this phase, they are aggregated
into a special PassivationException, otherwise thrown "as-is".
Yes, something like that makes sense. It's hard to know what is the
right way to handle startup errors. But what you outline above sounds ok.
/Rickard
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
