Dynamic ClassLoader not (always) correctly handling bundle updates
------------------------------------------------------------------
Key: SLING-1874
URL: https://issues.apache.org/jira/browse/SLING-1874
Project: Sling
Issue Type: Bug
Components: Commons
Affects Versions: Commons ClassLoader 1.2.0
Reporter: Felix Meschberger
Assignee: Felix Meschberger
Fix For: Commons ClassLoader 1.2.2
The Dynamic ClassLoader reacts to updates to bundles which are used by the
PackageAdmin based class loader by cycling the service and thus ensuring
classes are loaded again from the correct location.
To this avail these bundle events are handled
UNRESOLVED: If the unresolved bundle was used, cycle the service
RESOLVED: If there was an unresolved package from the resolved bundle, cycle
the service
This setup fails to cycle the service if a used bundle was re-wired due to an
update/re-wiring of a used bundle. The reason for this is, that such a
dependent re-wiring causes the bundle to stopp (STOPPING, STOPPED events),
resolve (RESOLVED event) and started (STARTING, STARTED events). There is no
UNRESOLVED event in this case.
This the RESOLVED event handling muss also cause service cycling in case the
now resolved bundle was used.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
