|Re: [jakartaee-platform-dev] [External] : Pending removal ofsecurity manager|
Hopefully there’s a Long enough grace period between deprecating that in OpenJDK and being able to Substitute it in Jakarta EE?
It looks like being only a Candidate now does not mean anything as to which Java Version really applies or fully removes security Manager (remember when Valhalla became a candidate? ;-P) but once it gets accepted by a JDK it may cause removal within 2 or 3 Java versions down the line.
Having helped customers from Java 9 to 11 in a SOAP-centric Environment with digital signatures I know this can be tricky and the more time we have to offer something in Jakarta EE to migrate to, the better.
I 100% agree with your position on the warnings. Perhaps requesting some control over this noise might be worth a comment, in the JEP.
If we have use-cases specific to EE, we should consider how we'd like to address those as well. We can do that in a number of ways. I suspect, the first thing, will be to enumerate where the EE specifications specifically call this out and decide how we would like to address these use-cases.
Getting back to the JEP, I am sure the JDK team would like to hear if there are specific use-cases that should be preserved and/or re-written especially those that might be universal to Java programs. Again, obtaining that feedback is exactly what the JEP process is designed to solicit.
On 4/15/2021 4:30 PM, arjan tijms wrote:
To unsubscribe from this list, visit https://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev__;!!GqivPVa7Brio!KRUFmjPeJ0n_GJjs6zgARB3Wzc1oJWADLIGbHn38hd92YjH_9Hg7etwr-0gjmRE$
Back to the top