[AXIS2-4349] Child first class loading

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.5.5, 1.6.0
• Assignee: Unassigned
• Reporter: Amila Chinthaka Suriarachchi
• Created: 15/May/09 13:59
• Updated: 02/Jul/16 13:34
• Resolved: 28/Dec/10 18:56

Description

Currently Axis2 follows the parent first class loading for service and module loading.

The reason for this is it uses DeploymentClassLoader loader which is extended from the ClassLoader class.

The loadClass method of the ClassLoader class looks like this.

protected synchronized Class<?> loadClass(String name, boolean resolve)
throws ClassNotFoundException
{
// First, check if the class has already been loaded
Class c = findLoadedClass(name);
if (c == null) {
try {
if (parent != null)

{ c = parent.loadClass(name, false); }

else

{ c = findBootstrapClass0(name); }

} catch (ClassNotFoundException e)

{ // If still not found, then invoke findClass in order // to find the class. c = findClass(name); }

}
if (resolve)

{ resolveClass(c); }

return c;
}

it first check for parent class loader classes and then for its classes. So we can add child first class loading simply reversing this order in a override loadClass method as follows.

protected synchronized Class<?> loadClass(String name, boolean resolve) throws ClassNotFoundException {

Class c = findLoadedClass(name);
if (c == null) {
try

{ c = findClass(name); }

catch (Exception e)

{ c = super.loadClass(name, resolve); }

}
return c;
}

Issue Links

• is depended upon by: AXIS2-4917 Provide proper documentation on deploying Axis2 in WebSphere