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". WDYT? Cheers -- Niclas Hedhman, Software Developer http://www.qi4j.org - New Energy for Java I live here; http://tinyurl.com/2qq9er I work here; http://tinyurl.com/2ymelc I relax here; http://tinyurl.com/2cgsug _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
