After debugging proxy creation I don't understand how the stacktrace attached to this bug happend, because
java.lang.ClassLoader.checkCert method does not care about the class name and only checks if all classes in the same package
have the same certificates. And because the Proxy has the same ProtectionDomain as the proxied class a certificate miss match should be impossible.

I guess i have to debug the original problem because everything looks fine on my side (with 2.4.4).