[
https://issues.apache.org/jira/browse/SLING-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12980130#action_12980130
]
Felix Meschberger commented on SLING-1925:
------------------------------------------
I tried to cover this aspect in my initial node: Basically this is just a door
opener for some internal HotSpot code which happens to exist on Sun/Oracle
JVMs. I don't expect other code to ever call something in the sun.reflect
package unless it is HotSpot code derived from the Sun/Oracle JVMs. Code never
needing this package is not affected.
So, at the end of the day it is not an implementation dependency.
Creating a VM specific fragment bundle would be another option. But that would
mean almost all users of Sling would have to install this bundle. Over the last
few weeks, I came to the conclusion, that the purity of setup is not worth the
price in this particular context. Consider it a special case, I do.
> Add sun.reflect to the default org.osgi.framework.bootdelegation system
> property
> --------------------------------------------------------------------------------
>
> Key: SLING-1925
> URL: https://issues.apache.org/jira/browse/SLING-1925
> 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
>
>
> There are known issues with recent Felix Framework versions around loading
> classes from the sun.reflect package to support Hotspot optimizations. See
> [1] for example.
> To easily fix these problems, we should add this package to the default setup
> of the org.osgi.framework.bootdelegation system property. This helps a lot on
> Sun JVMs but does not hurt at all on non-Sun JVMs.
> [1] http://www.mail-archive.com/[email protected]/msg07721.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
