You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2011/01/27 12:19:43 UTC
[jira] Resolved: (SLING-1959) Ensure correct parent class loader
for boot delegation
[ https://issues.apache.org/jira/browse/SLING-1959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger resolved SLING-1959.
--------------------------------------
Resolution: Fixed
Assignee: Felix Meschberger
Defined the property in the default sling.properties file in Rev. 1064083
> Ensure correct parent class loader for boot delegation
> ------------------------------------------------------
>
> Key: SLING-1959
> URL: https://issues.apache.org/jira/browse/SLING-1959
> Project: Sling
> Issue Type: Improvement
> Components: Launchpad
> Affects Versions: Launchpad Base 2.2.0
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: Launchpad Base 2.2.2
>
>
> The OSGi specification allows the definition of which class loader to use for boot delegation using the "org.osgi.framework.bundle.parent" framework property.
> Generally, when running the framework as the "single" application in a JVM, there is no need to ever think about this property. But if the framework is embedded in some other application, e.g. in a servlet container such as when the Sling Launchpad Web Application is used, the default parent class loader configuration might be the wrong one.
> For Sling we should set this property to "framework" to include the whole classloader tree for finding classes through boot delegation.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.