[jboss-osgi-issues] [JBoss JIRA] Resolved: (JBOSGI-286) Investigate classloading of javax.* classes

[Thomas Diesler (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBOSGI-286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas Diesler resolved JBOSGI-286.
-----------------------------------

    Resolution: Done


Running org.jboss.test.osgi.jbosgi286.OSGi286TestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 7.482 sec


> Investigate classloading of javax.* classes
> -------------------------------------------
>
>                 Key: JBOSGI-286
>                 URL: https://jira.jboss.org/jira/browse/JBOSGI-286
>             Project: JBoss OSGi
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Core Framework
>            Reporter: Thomas Diesler
>            Assignee: Thomas Diesler
>             Fix For: Framework 1.0.0 Alpha3
>
>
> The Framework must always delegate any package that starts with java. to the parent class loader.
> Certain Java virtual machines, also SUN's VMs, appear to make the erroneous assumption that the delegation to the parent class loader always occurs.
> This implicit assumption of strictly hierarchical class loader delegation can result in NoClassDefFoundErrors. This happens if the virtual machine
> implementation expects to find its own implementation classes from any arbitrary class loader, requiring that packages loaded from the boot class
> loader not be restricted to only the java.* packages. Other packages that must be loaded from the boot class loader can therefore be specified with the System property:
>    org.osgi.framework.bootdelegation
> The packages in javax.* are NOT on the boot classpath by default

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira