Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
1.4.0, 1.5.0
-
None
Description
Hi,
in BrowserConnectionManager.load
and in
Utils.serialize / deserialize
we recognized that the ClassLoader is modified without conserving / resetting it to the previous one at the end.
This conflicted with our class loading mechanisms ... streaming from our own class store.
As a quick fix for testing, we could do for example the following; however, this is not a real solution:
public static String serialize( Object o )
{
String s = null;
Thread cur_thrd = Thread.currentThread(); //patch reset current class loader
ClassLoader cur_thrd_cl = cur_thrd.getContextClassLoader();
try
finally
{ cur_thrd.setContextClassLoader(cur_thrd_cl); } return s;
}
=> Is there a better way?
Thanks and regards,
Karsten