In fact several problems exists:
- to prevent lock on filesystem because of memory leak, a method 'close' has been introduced in PetalsClassLoader to force to close the JAR files of classloader. I think that this tricky method should be removed (
PETALSESBCONT-189).
- The bootstrap classloader is created on initialization of the installer. The component classloader is created when installing the component and freed on component uninstallation. It's right, but the bootstrap classloader is also deleted on component uninstallation.
I think that to fix the problem, the boostrap classloader should be freed on finalization of the installer.
In fact several problems exists:
PETALSESBCONT-189).I think that to fix the problem, the boostrap classloader should be freed on finalization of the installer.
- to prevent lock on filesystem because of memory leak, a method 'close' has been introduced in PetalsClassLoader to force to close the JAR files of classloader. I think that this tricky method should be removed (
- The bootstrap classloader is created on initialization of the installer. The component classloader is created when installing the component and freed on component uninstallation. It's right, but the bootstrap classloader is also deleted on component uninstallation.
I think that to fix the problem, the boostrap classloader should be freed on finalization of the installer.PETALSESBCONT-189).