You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@stanbol.apache.org by "Rupert Westenthaler (Created) (JIRA)" <ji...@apache.org> on 2012/01/18 18:46:40 UTC
[jira] [Created] (STANBOL-464) The Bundle Provider MUST NOT
uninstall resources if a Bundle is STOPED
The Bundle Provider MUST NOT uninstall resources if a Bundle is STOPED
----------------------------------------------------------------------
Key: STANBOL-464
URL: https://issues.apache.org/jira/browse/STANBOL-464
Project: Stanbol
Issue Type: Bug
Components: Commons
Reporter: Rupert Westenthaler
Assignee: Rupert Westenthaler
The Bundle Provider adds support to the Apache Sling OSGI Installer Framework that installs Resources provided by OSGI Bundles.
Currently Bundle Events are processed like follows:
* STARTED: all installable resources will be installed
* STOPPED: all installable resource will be uninstalled
* UPDATED: all installable resources will be first uninstalled and than installed
The issue is with uninstalling resources if a Bundle is STOPPED because this event is also sent for all bundles if the OSGI Environment is shutting down. The affected resources will be installed again on the next start however this behavior is not intended and can cause a lot of side effects such as that Services that are created by installed configurations will get different Service PIDs on every restart.
To solve this uninstalling of resources MUST only be performed if a Bundle is UNINSTALLED. This event is only sent if a Bundle is programmatic or manually removed form the OSGI environment and can be never sent by a normal life cycle activity.
Thanks to David Riccitelli in helping me to identify this as source for a lot of hart to track down bugs within Stanbol.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (STANBOL-464) The Bundle Provider MUST NOT
uninstall resources if a Bundle is STOPPED
Posted by "Rupert Westenthaler (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/STANBOL-464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rupert Westenthaler resolved STANBOL-464.
-----------------------------------------
Resolution: Fixed
Fixed with Revision 1232976
> The Bundle Provider MUST NOT uninstall resources if a Bundle is STOPPED
> -----------------------------------------------------------------------
>
> Key: STANBOL-464
> URL: https://issues.apache.org/jira/browse/STANBOL-464
> Project: Stanbol
> Issue Type: Bug
> Components: Commons
> Reporter: Rupert Westenthaler
> Assignee: Rupert Westenthaler
>
> The Bundle Provider adds support to the Apache Sling OSGI Installer Framework that installs Resources provided by OSGI Bundles.
> Currently Bundle Events are processed like follows:
> * STARTED: all installable resources will be installed
> * STOPPED: all installable resource will be uninstalled
> * UPDATED: all installable resources will be first uninstalled and than installed
> The issue is with uninstalling resources if a Bundle is STOPPED because this event is also sent for all bundles if the OSGI Environment is shutting down. The affected resources will be installed again on the next start however this behavior is not intended and can cause a lot of side effects such as that Services that are created by installed configurations will get different Service PIDs on every restart.
> To solve this uninstalling of resources MUST only be performed if a Bundle is UNINSTALLED. This event is only sent if a Bundle is programmatic or manually removed form the OSGI environment and can be never sent by a normal life cycle activity.
> Thanks to David Riccitelli in helping me to identify this as source for a lot of hart to track down bugs within Stanbol.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (STANBOL-464) The Bundle Provider MUST NOT
uninstall resources if a Bundle is STOPPED
Posted by "Rupert Westenthaler (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/STANBOL-464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rupert Westenthaler updated STANBOL-464:
----------------------------------------
Summary: The Bundle Provider MUST NOT uninstall resources if a Bundle is STOPPED (was: The Bundle Provider MUST NOT uninstall resources if a Bundle is STOPED)
> The Bundle Provider MUST NOT uninstall resources if a Bundle is STOPPED
> -----------------------------------------------------------------------
>
> Key: STANBOL-464
> URL: https://issues.apache.org/jira/browse/STANBOL-464
> Project: Stanbol
> Issue Type: Bug
> Components: Commons
> Reporter: Rupert Westenthaler
> Assignee: Rupert Westenthaler
>
> The Bundle Provider adds support to the Apache Sling OSGI Installer Framework that installs Resources provided by OSGI Bundles.
> Currently Bundle Events are processed like follows:
> * STARTED: all installable resources will be installed
> * STOPPED: all installable resource will be uninstalled
> * UPDATED: all installable resources will be first uninstalled and than installed
> The issue is with uninstalling resources if a Bundle is STOPPED because this event is also sent for all bundles if the OSGI Environment is shutting down. The affected resources will be installed again on the next start however this behavior is not intended and can cause a lot of side effects such as that Services that are created by installed configurations will get different Service PIDs on every restart.
> To solve this uninstalling of resources MUST only be performed if a Bundle is UNINSTALLED. This event is only sent if a Bundle is programmatic or manually removed form the OSGI environment and can be never sent by a normal life cycle activity.
> Thanks to David Riccitelli in helping me to identify this as source for a lot of hart to track down bugs within Stanbol.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira