It's been a long time ago.
Had someone had the time to think about this:
Am 29.10.2011 13:17, schrieb Sebastian Sickelmann:
Sorry i linked the wrong webrev for Solution 3.
Am 27.10.2011 16:50, schrieb Sebastian Sickelmann:
Some time ago (see below) i ask what would be the right solution to
ref
Changeset: d27f0b2f1476
Author:coffeys
Date: 2011-11-23 14:55 +
URL: http://hg.openjdk.java.net/jdk8/tl/jdk/rev/d27f0b2f1476
7102369: remove java.rmi.server.codebase property parsing from registyimpl
7094468: rmiregistry clean up
Reviewed-by: smarks
! src/share/classes/sun/rmi/
Thanks for the review.
> I think a better approach would be to add check{Client,Server}Trusted methods
> that return a result. For example, something like (I believe that changing the
> X509Certificate[] parameter allows us to overload the method with a different
> return type):
>
> public TrustM
Changeset: 7eb0debca9b3
Author:chegar
Date: 2011-11-23 12:30 +
URL: http://hg.openjdk.java.net/jdk8/tl/jdk/rev/7eb0debca9b3
6776144: java/lang/ThreadGroup/NullThreadName.java fails with Thread group is
not destroyed ,fastdebug LINUX
Reviewed-by: chegar, dholmes
Contributed-by:
Changeset: 82151e860a64
Author:xuelei
Date: 2011-11-23 03:40 -0800
URL: http://hg.openjdk.java.net/jdk8/tl/jdk/rev/82151e860a64
7113275: compatibility issue with MD2 trust anchor and old X509TrustManager
Summary: also reviewed by dennis...@oracle.com
Reviewed-by: mullan
! src/share
