[
https://issues.apache.org/jira/browse/SLING-7109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16155085#comment-16155085
]
Carsten Ziegeler commented on SLING-7109:
-----------------------------------------
Actually my whole assumption seems to be wrong as an update sends an unresolved
event and (if packages are refreshed) a resolved event. Both are already
covered by our code. Need some further testing whether this code change fixes
the problem nevertheless
> Classloader not updated when bundle is updating
> -----------------------------------------------
>
> Key: SLING-7109
> URL: https://issues.apache.org/jira/browse/SLING-7109
> Project: Sling
> Issue Type: Bug
> Components: Commons
> Affects Versions: Commons ClassLoader 1.4.0
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Commons ClassLoader 1.4.2
>
>
> The class loader is not updated/refreshed if a bundle is updated.
> Imagine the following use case:
> A jsp is compiled. It has an import to an existing class, however it is using
> a field in that class which does not exist. This creates a compilation
> problem. However from the pov of the classloader everything is fine as the
> class exists.
> Now the bundle is updated and the class in question contains the field.
> However, the classloader is not refreshed/updated and therefore the jsp
> compilation still fails.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
