On 31/07/2021 04:04, Peter Firmstone wrote:
Allan has advised when finalizers are removed, it will be practical to
use Agents to instrument public API to implement an authorization
layer, this is try, so can it be coordinated with JEP 411 et al?
Our exchange was about instrumenting construct
I'm potentially watching many years of development efforts burn, due to
JEP 411 and trying to find a way to save it, I don't refer to it as
fun. Frustrating, infuriating, irritating, anger, that would more
accurately describe the emotions current circumstances create.
I'll be focusing only on
> Hi all,
>
> could you please review this big tedious and trivial(-ish) patch which moves
> `sun.hotspot.WhiteBox` and related classes to `jdk.test.whitebox` package?
>
> the majority of the patch is the following substitutions:
> - `s~sun/hotspot/WhiteBox~jdk/test/whitebox/WhiteBox~g`
> - `s
On Sat, 31 Jul 2021 20:42:10 GMT, Igor Ignatyev wrote:
>> Hi all,
>>
>> could you please review this big tedious and trivial(-ish) patch which moves
>> `sun.hotspot.WhiteBox` and related classes to `jdk.test.whitebox` package?
>>
>> the majority of the patch is the following substitutions:
>>
Hi Michael,
I’m not sure what exact problem you ran into, but looking at the implementation
of PKCS12KeyStore at [1] the friendly name is hardcoded to be encoded in
BMPString:
bagAttr1.putOID(PKCS9FriendlyName_OID);
DerOutputStream bagAttrContent1 = new DerOutputStream()
Hi Ron,
So far we have dealt with CORBA (external library), pack200 (working on
an external lib) and to support Java 17, removed some Activation class
dependencies (we don't use RMID, so grabbed the missing Activation
classes from Apache Harmony), thankfully these were not challenging,
althou
