Bug 24837 - [launcher] Extension classes are not reachable from plugin code
Summary: [launcher] Extension classes are not reachable from plugin code
Status: RESOLVED DUPLICATE of bug 30919
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Resources (show other bugs)
Version: 2.0.2   Edit
Hardware: PC Windows All
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Platform-Resources-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-10-16 11:10 EDT by JP Moresmau CLA
Modified: 2003-07-22 11:38 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description JP Moresmau CLA 2002-10-16 11:10:46 EDT
Some packages need to be put in JRE_HOME/lib/ext, especially in JDK 1.3 (JAAS 
and JCE classes, for examples). Any other location will not work. Loading them 
in a new ClassLoader from that location will not work: they need to be accessed 
from the orignal class loader. However, org.eclipse.platform.launcher.Main 
creates a new ClassLoader to start loading Eclipse and its plugins with no 
parent, which means the extension classes cannot be reached from our plugin 
code, which means we can't use things like JAAS or JCE!
As a short term solution we have modified Main.java to use the classloader that 
loaded Main.class as the parent to BootClassLoader. I understand that the 
current way of doing it simplifies a lot the issues of classloading and class 
conflict (classes loaded from the CLASSPATH), but it would be good to have a 
way to turn that behaviour off for the whole Eclipse or for some plugins.

Thanks!

JP Moresmau
http://www.soamai.com
Comment 1 John Arthorne CLA 2003-07-22 11:38:32 EDT

*** This bug has been marked as a duplicate of 30919 ***