BugRat Report #189 - Classloader search order.

[BugRat Mail System]

Report #189 Details

Project: Tomcat
Category: Feature Requests
SubCategory: Enhancement
Class: suggest
State: received
Priority: high
Severity: critical
Confidence: public
Environment: 
   Release: 3.2 4b
   JVM Release: jdk 1.2.2
   Operating System: NT
   OS Release: 4.0
   Platform: window

Synopsis: 
Classloader search order.

Description:
The loadClass() in loader/AdaptiveClassLoader class has 

We are using Tomcat as our servlet container for our servlet application. We also uses 
XML with different parser which cause package and class name conllisions with Tomcat.
Tomcat's class loader has no help in this case because or its loading ordering. 
 Tomcat classload has the following order for loading a class:
   cache, 
   parent,  
   system, 
   web apps repository

There is no way to have our classes loaded except to
change Tomcat's code. If we define our jar file in Tomcat's
classpath, Tomcat won't function correctly. So we have to
change Tomcat's order as: cache, repository, parent, then
system classpath. It works. 
In general, if we want to keep classes in an application boundry, shouldn't we load 
classes in web apps repository before loading from its parent? or system?

M. Balcom

Title: BugRat Report # 189

BugRat Report # 189

Project: Tomcat	Release: 3.2 4b
Category: Feature Requests	SubCategory: Enhancement
Class: suggest	State: received
Priority: high	Severity: critical
Confidence: public

Submitter: M. Balcom ( [EMAIL PROTECTED] )
Date Submitted: Oct 1 2000, 06:23:17 CDT
Responsible: Z_Tomcat Alias ( [EMAIL PROTECTED] )

Synopsis:

Classloader search order.

Environment: (jvm, os, osrel, platform)

jdk 1.2.2, NT, 4.0, window

Additional Environment Description:

Report Description:

The loadClass() in loader/AdaptiveClassLoader class has We are using Tomcat as our servlet container for our servlet application. We also uses XML with different parser which cause package and class name conllisions with Tomcat. Tomcat's class loader has no help in this case because or its loading ordering. Tomcat classload has the following order for loading a class: cache, parent, system, web apps repository There is no way to have our classes loaded except to change Tomcat's code. If we define our jar file in Tomcat's classpath, Tomcat won't function correctly. So we have to change Tomcat's order as: cache, repository, parent, then system classpath. It works. In general, if we want to keep classes in an application boundry, shouldn't we load classes in web apps repository before loading from its parent? or system? M. Balcom

View this Report online...

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]