felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Felix Meschberger (JIRA)" <j...@apache.org>
Subject [jira] Closed: (FELIX-169) Shutdown of Felix through Felix.shutdown() does not call custom activator stop methods
Date Tue, 07 Nov 2006 07:56:50 GMT
     [ http://issues.apache.org/jira/browse/FELIX-169?page=all ]

Felix Meschberger closed FELIX-169.

Thanks alot. Closing this issue then.

> Shutdown of Felix through Felix.shutdown() does not call custom activator stop methods
> --------------------------------------------------------------------------------------
>                 Key: FELIX-169
>                 URL: http://issues.apache.org/jira/browse/FELIX-169
>             Project: Felix
>          Issue Type: Bug
>            Reporter: Felix Meschberger
>         Assigned To: Richard S. Hall
>         Attachments: FELIX-169.diff, FELIX-169_2.diff
> When starting Felix through Felix.start() a list of BundleActivator objects may be handed
in. Additionally, the SystemBundle adds some more BundleActivators (e.g. the URLHandlersActivator.
When stopping Felix through the SystemBundle.stop() method, a separate thread is started,
which calls the Felix.shutdown() method, which ultimately calls back into the SystemBundle.stop()
method, which now - amongst other things - calls the BundleActivator.stop() method of the
additional BundleActivators.
> If shutting Felix down through Felix.shutdown() directly, a separate thread is not started,
and hence the BundleActivator.stop() methods are not called.
> I assume, the test for the m_shutdownThread field in the SystemBundle.stop method is
superfluous as this field is only set then Felix is stopped through the system bundle.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message