As you can not change the jdk code I think such a workaround is acceptable.
Btw. It is a good practice to save the old ThreadContextClassLoader and
restore it after the call.
Christian
Am 24.04.2012 22:08, schrieb Hervé BARRAULT:
Hi, i did a really ugly quick fix using ThreadContextClassLoader and
it is working (using resolveClass for ObjectInputStream).
I say ugly because it is still based on class name [not OSGI
compliant] but it validates the ThreadContextClassLoader "Workaround".
Thanks
Regards
hervé
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
Talend Application Integration Division http://www.talend.com
