<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
On 19/04/2023 07:36, Eirik Bjørsnøs wrote:<br>
<blockquote type="cite" cite="mid:CA+pBWhuZHdgkqnoJNA-OzXB2xz4Ytqy6B9A9RQajc4igYasDXQ@mail.gmail.com">
<div dir="ltr">
<div class="gmail_quote">
<div><br>
<br>
</div>
<div>To summarize, I'm hopeful that removing 'Identity' and
friends have limited effect on Java EE 8 implementations and
apps and that workarounds exist for problems which may
occur. Apps using the deprecated APIs in EJBContext would of
course need to be updated, but that's a straightforward
replacement job.</div>
</div>
</div>
</blockquote>
<br>
Sean put it well when he said we are in a "holding pattern" on these
APIs right now. I don't think it's a holding pattern for perpetuity
but I think it will take time for the big proprietary and legacy app
servers to move beyond Java EE 8 and not expect build+deploy with
new JDK releases at the same time. From the JDK side, it is annoying
to be keep around classes such as java.security.Identity that have
been deprecated since 1998. Ideally enhanced deprecation would have
been introduced long before Java 9 and that Java EE or EJB would
have removed its dependence on this API a long time ago. I think we
are where we are and it should be possible to re-visit this one in a
few releases.<br>
<br>
-Alan<br>
</body>
</html>