[
https://issues.apache.org/jira/browse/FELIX-1193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12728738#action_12728738
]
Richard S. Hall commented on FELIX-1193:
----------------------------------------
Sahoo, RFC 132 says to use the boot class loader (which is the default). It
doesn't go into details saying what this should be (i.e., null or not). From my
perspective, we should try to use whatever is customarily used on the given
platform. So, if null is used for boot, then it would be nice if we could use
null so that we are consistent for the platform. If some other class loader is
used, then we should use that. So, in that regard, I think following some form
of your suggestion makes sense. Even then, I still don't think this will
eliminate the need for a workaround.
Stuart, you are probably correct, we will need to use secure actions to get the
class loader. I will reopen this issue to remind me to do that.
> Implement org.osgi.framework.bundle.parent from RFC 132
> -------------------------------------------------------
>
> Key: FELIX-1193
> URL: https://issues.apache.org/jira/browse/FELIX-1193
> Project: Felix
> Issue Type: New Feature
> Components: Framework, Specification compliance
> Affects Versions: felix-1.8.0
> Reporter: Richard S. Hall
> Assignee: Richard S. Hall
> Fix For: felix-2.0.0
>
>
> The new standard framework launching and embedding API introduced a property
> (org.osgi.framework.bundle.parent) to configure the class loader used for
> boot delegation. We should modify Felix to support this property.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
