Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
5.0M5
-
None
Description
PropertyEditorManager.findEditor() always uses the target class loader to locate the editor, while it should use thread context class loader when a particular editor is not found the the target class loader.
Here's the test demonstrating the problem:
import java.beans.*;
import java.net.*;
public class Test {
public static void main(String[] args) {
try {
PropertyEditorManager.setEditorSearchPath(new String[]
);
ClassLoader editorLoader = new URLClassLoader(new URL[]
);
Thread.currentThread().setContextClassLoader(editorLoader);
PropertyEditor editor = PropertyEditorManager.findEditor(MyClass.class);
if (editor == null)
else
{ String editorName = editor.getClass().getName(); System.out.println(editorName.equals("myPackage.MyClassEditor") ? "SUCCESS" : ("FAIL: " + editorName)); }} catch (Throwable e)
{ System.out.print("ERROR: "); e.printStackTrace(System.out); } }
}
class MyClass {
}
package myPackage;
public class MyClassEditor extends java.beans.PropertyEditorSupport {
}
Compiled MyClassEditor.class should be put to ./editor/myPackage/MyClassEditor.class for the test to work.
Output on RI:
SUCCESS
Output on Harmony:
FAIL: null
The reason the test fails is the editor is available in other classloader than the original class. That classloader is preliminarily specified by Thread.currentThread().setContextClassLoader(), but Harmony implementation doesn't use it. To fix, the classloader handling mechanism in PropertyEditorManager.findEditor() needs to be changed.
This testcase was derived from org.apache.geronimo.common.propertyeditor.PropertyEditors.findEditor(String, ClassLoader) method.
This issue prevents Geronimo 2.1-snapshot from starting on Harmony.
Attachments
Attachments
Issue Links
- is related to
-
GERONIMO-3814 NPE in GBeanOverride
- Closed