Bug 45726 - check the value of the default context class loader
Summary: check the value of the default context class loader
Status: RESOLVED DUPLICATE of bug 30919
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: Incubator (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Thomas Watson CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-10-29 09:13 EST by Jeff McAffer CLA
Modified: 2005-09-27 09:12 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jeff McAffer CLA 2003-10-29 09:13:51 EST 
We should confirm that the context classloader has an appropriate value.

see bug 30919 for details
Comment 1 Thomas Watson CLA 2004-01-26 17:25:44 EST 
The default context class loader in the Framework is the application 
classloader which includes the startup.jar -> extension classloader -> boot 
classloader.

This is probably not the right choice.  Question is what did eclipse used to 
use as the default context class loader?  The boot classloader?  The default 
context class loader is set by the parent thread of eclipse so I would imagine 
the EclipseStarter would have to set the context classloader to whatever it 
wants to use as the default class loader for the rest of eclipse.
Comment 2 Jeff McAffer CLA 2004-01-28 00:14:17 EST 
I do not recall classic eclipse doing anything in this area.  Perhaps the 
subject never came up?  Seems like the right answer might be the PARENT 
classloader as defined in RFC70.

Seems also that this would have to be set by EclipseStarter.  Basiclaly before 
a thread is forked.
Comment 3 Thomas Watson CLA 2004-05-06 15:02:56 EDT 
What do we want to do here?  Set the context classloader to the Bundle 
ParentClassLoader?

From bug 30919 it appears eclipse 2.1 has the context classloader set to the 
application classloader.  Bug 30919 raises the question of whether this is 
correct or not.  It seems to be incorrect since there is no other way to get 
access to the application classloader from a plugin/bundle in eclipse.

If we change this behavior in 3.0 will it be an issue for backwards 
compatiblity?
Comment 4 Thomas Watson CLA 2004-05-07 15:01:08 EDT 
Decided against making any changes for 3.0 in this area.  Duping to 30919 
where the real discussion is about what the proper value of the default 
context classloader should be.

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