Issue480017

classification

Title:	Proxy supers are loaded from syspath.
Type:		Severity:	normal
Components:	Core	Versions:
		Milestone:

process

Status:	closed	Resolution:	fixed
Dependencies:		Superseder:
Assigned To:	cgroves	Nosy List:	bckfnn, cgroves
Priority:	high	Keywords:

Created on 2001-11-09.14:43:32 by bckfnn, last changed 2006-07-31.23:15:08 by cgroves.

Files
File name	Uploaded	Description	Edit	Remove
480017bugtest.diff	cgroves, 2006-07-30.00:39:52
480017trunk.diff	cgroves, 2006-07-31.23:15:08

Messages
msg456 (view)	Author: Finn Bock (bckfnn)	Date: 2001-11-09.14:43:32
When a superclass/interface of a proxy is loaded by a custom classloader, the sys.path java loader is still tried before the superclass/interface classloader is tried. That is wrong, the order should be reversed so that the referent classloaders is tried before resorting to the sys.path java loader.
msg457 (view)	Author: Finn Bock (bckfnn)	Date: 2001-11-09.14:50:43
Logged In: YES user_id=4201 Added as test338.
msg458 (view)	Author: Charlie Groves (cgroves)	Date: 2006-07-30.00:39:52
Logged In: YES user_id=1174327 The attached patch for trunk just moves any added classloaders to the front of the list to be tried. This just means that since the syspath classloader is always added first, any referent classloaders that are added later will be tried before it. The bugtest patch just renables the bugtest that was testing this.

History
Date	User	Action	Args
2001-11-09 14:43:32	bckfnn	create