[
https://issues.apache.org/jira/browse/SLING-1435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-1435.
-------------------------------------
Resolution: Fixed
Added a workaround in revision 921377 which simply removes the old class if a
NoClassDefFoundError is thrown during script
execution.
While the solution does not look nice it works, therefore I'm closing the bug :)
> After a NoClassDefError classes are still not found even if they have been
> installed in the meantime with Java 6
> ----------------------------------------------------------------------------------------------------------------
>
> Key: SLING-1435
> URL: https://issues.apache.org/jira/browse/SLING-1435
> Project: Sling
> Issue Type: Bug
> Components: Scripting
> Affects Versions: Scripting JSP 2.0.8
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Scripting JSP 2.0.10
>
>
> Scenario - note that this works fine with Java 5, but on Java 6 we have:
> - A jsp instanties a class from bundle A with the new operator
> - JSP is loaded - everything is working fine
> - Bundle A is uninstalled
> - JSP invocation results in NoClassDefFoundError (which is expected)
> - Bundle A is installed
> - JSP is invoked and as soon as the new operator is called a
> NoClassDefFoundError is called
> It seems that Java 6 behaves differently than Java 5: The jsp can be loaded
> and executed, but as soon as the class from Bundle A is used, Java 6
> memorieses that the class was gone inbetween and it is not possible to update
> this state somehow. All involved classloaders are not queried anymore
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
