<div dir="ltr"><div><div><div><div dir="ltr"><div dir="ltr"><div>TLDR: Payara 5 seems to work fine with java.security.{Certificate,Identity,IdentityScope,Signer} classes removed</div><div><br></div></div><div class="gmail_quote"></div></div></div><div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;padding-left:1ex;border-left-color:rgb(204,204,204)"><div dir="ltr"><div class="gmail_quote"><div>I have been exploring the effects of removing these APIs on JBoss Wildfly 20, the latest version to support Java EE 8.</div></div></div></blockquote><div><br></div></div></div></div><div>Repeating the experiment using Payara 5 shows similar results to Wildfly 20. EJBs calling methods in EJBContext continue to work as expected with 21-internal. If the deprecated EJBContext.getCallerIdentity() method is called, an exception is thrown (not because of the API removal, but because Payara decided to throw for this method): </div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Caused by: java.lang.RuntimeException: getCallerIdentity() is deprecated, please use getCallerPrincipal().<br> at com.sun.ejb.containers.EJBContextImpl.getCallerIdentity(EJBContextImpl.java:382)</blockquote><div><br></div><div>I had to make a minor change to Payara 5 to make it run on Java 21, which was to upgrade ASM from 9.4 to 9.5. I'll consider a PR for this, although it seems they don't plan any more releases of Payara 5 Community edition. Maybe a PR can prod them to upgrade the Enterprise offering.</div><div><br></div><div>Cheers,</div><div>Eirik. </div>
</div>