You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@plc4x.apache.org by "Łukasz Dywicki (Jira)" <ji...@apache.org> on 2022/07/11 10:28:00 UTC
[jira] [Updated] (PLC4X-350) OSGi activators won't unregister any services other than the last one
[ https://issues.apache.org/jira/browse/PLC4X-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Łukasz Dywicki updated PLC4X-350:
---------------------------------
Fix Version/s: 0.10.0
> OSGi activators won't unregister any services other than the last one
> ---------------------------------------------------------------------
>
> Key: PLC4X-350
> URL: https://issues.apache.org/jira/browse/PLC4X-350
> Project: Apache PLC4X
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.10.0
> Reporter: Thomas Hentschel
> Assignee: Łukasz Dywicki
> Priority: Minor
> Fix For: 0.10.0
>
>
> It looks as if the OSGI bundle activators in plc4x/plc4j/osgi/src/main/java/org/apache/plc4x/java/osgi won't unregister any services (driver / transport) other than the last registered driver/transport when the bundle is stopped.
> I believe the implementation should keep a List of 'ServiceRegistration<PlcDriver>' instead of the single instance var. This way, the activator 'stop()' method can loop over the list and unregister all services registered in the 'start()' method
--
This message was sent by Atlassian Jira
(v8.20.10#820010)