From iris.clark at oracle.com Thu May 6 17:23:37 2021 From: iris.clark at oracle.com (Iris Clark) Date: Thu, 6 May 2021 17:23:37 +0000 Subject: JSR 392 (Java SE 17): JEP Propose to Target: 409: Sealed Classes Message-ID: The following JEP with scope "SE" has been proposed to target JDK 17: 409: Sealed Classes https://openjdk.java.net/jeps/409 Summary: Enhance the Java programming language with sealed classes and interfaces. Sealed classes and interfaces restrict which other classes or interfaces may extend or implement them. The announced deadline for feedback to jdk-dev is Wed 12 May 23:59 UTC: https://mail.openjdk.java.net/pipermail/jdk-dev/2021-May/005508.html If there are no unresolved objections at that time, then the JEP will be moved to the Targeted state, indicating that the feature is expected to appear in the specified release of the JDK Project. For more information about states, see the JEP Process document: https://openjdk.java.net/jeps/1 A dashboard that lists JEPs with "SE" scope may be found via a link on this page: https://openjdk.java.net/projects/jdk/17/spec/ Thanks, Iris From iris.clark at oracle.com Thu May 6 23:01:33 2021 From: iris.clark at oracle.com (Iris Clark) Date: Thu, 6 May 2021 23:01:33 +0000 Subject: New Candidate JEP: 415: Context-Specific Deserialization Filters Message-ID: The following JEP with scope "SE" has been moved to the Candidate state: 415: Context-Specific Deserialization Filters https://openjdk.java.net/jeps/415 Summary: Allow applications to configure context-specific and dynamically-selected deserialization filters via a JVM-wide filter factory that is invoked to select a filter for each individual deserialization operation. A JEP in the Candidate state is a feature deemed worthy of consideration by the JDK Project, but with no commitment to deliver the feature in any particular release of the JDK Project. Later, the JEP may be moved to the Targeted state, which indicates that the feature is expected to appear in a specific release of the JDK Project. For more information about states, see the JEP Process document: https://openjdk.java.net/jeps/1 A JEP with "SE" scope that reaches the Targeted state will be listed in the Specification of the Java SE Platform JSR which corresponds to the targeted JDK Project release. A dashboard that lists JEPs with "SE" scope may be found via a link on this page: https://openjdk.java.net/projects/jdk/17/spec/ Thanks, Iris From iris.clark at oracle.com Mon May 17 23:00:01 2021 From: iris.clark at oracle.com (Iris Clark) Date: Mon, 17 May 2021 23:00:01 +0000 Subject: JSR 392 (Java SE 17): JEP proposed to Target: 407: Remove RMI Activation Message-ID: The following JEP with scope "SE" has been proposed to target JDK 17: 407: Remove RMI Activation https://openjdk.java.net/jeps/407 Summary: Remove the Remote Method Invocation (RMI) Activation mechanism, while preserving the rest of RMI. The announced deadline for feedback to jdk-dev is Mon 24 May 23:59 UTC: https://mail.openjdk.java.net/pipermail/jdk-dev/2021-May/005558.html If there are no unresolved objections at that time, then the JEP will be moved to the Targeted state, indicating that the feature is expected to appear in the specified release of the JDK Project. For more information about states, see the JEP Process document: https://openjdk.java.net/jeps/1 A dashboard that lists JEPs with "SE" scope may be found via a link on this page: https://openjdk.java.net/projects/jdk/17/spec/ Thanks, Iris From iris.clark at oracle.com Wed May 19 15:56:55 2021 From: iris.clark at oracle.com (Iris Clark) Date: Wed, 19 May 2021 15:56:55 +0000 Subject: JSR 392 (Java SE 17): JEP Proposed to Target: 403: Strongly Encapsulate JDK Internals Message-ID: The following JEP with scope "SE" has been proposed to target JDK 17: 403: Strongly Encapsulate JDK Internals https://openjdk.java.net/jeps/403 Summary: Strongly encapsulate all internal elements of the JDK, except for critical internal APIs such as sun.misc.Unsafe. It will no longer be possible to relax the strong encapsulation of internal elements via a single command-line option, as was possible in JDK 9 through JDK 16. The announced deadline for feedback to jdk-dev is Tue 25 May 23:59 UTC: https://mail.openjdk.java.net/pipermail/jdk-dev/2021-May/005571.html If there are no unresolved objections at that time, then the JEP will be moved to the Targeted state, indicating that the feature is expected to appear in the specified release of the JDK Project. For more information about states, see the JEP Process document: https://openjdk.java.net/jeps/1 A dashboard that lists JEPs with "SE" scope may be found via a link on this page: https://openjdk.java.net/projects/jdk/17/spec/ Thanks, Iris From iris.clark at oracle.com Thu May 20 19:43:40 2021 From: iris.clark at oracle.com (Iris Clark) Date: Thu, 20 May 2021 19:43:40 +0000 Subject: JSR 392 (Java SE 17): JEP Proposed to Target: 406: Pattern Matching for switch (Preview) Message-ID: The following JEP with scope "SE" has been proposed to target JDK 17: 406: Pattern Matching for switch (Preview) https://openjdk.java.net/jeps/406 Summary: Enhance the Java programming language with pattern matching for switch expressions and statements, along with extensions to the language of patterns. Extending pattern matching to switch allows an expression to be tested against a number of patterns, each with a specific action, so that complex data-oriented queries can be expressed concisely and safely. The announced deadline for feedback to jdk-dev is Wed 26 May 23:59 UTC: https://mail.openjdk.java.net/pipermail/jdk-dev/2021-May/005579.html If there are no unresolved objections at that time, then the JEP will be moved to the Targeted state, indicating that the feature is expected to appear in the specified release of the JDK Project. For more information about states, see the JEP Process document: https://openjdk.java.net/jeps/1 A dashboard that lists JEPs with "SE" scope may be found via a link on this page: https://openjdk.java.net/projects/jdk/17/spec/ Thanks, Iris From iris.clark at oracle.com Sat May 22 01:24:01 2021 From: iris.clark at oracle.com (Iris Clark) Date: Sat, 22 May 2021 01:24:01 +0000 Subject: JSR 392 (Java SE 17): JEP Proposed to Target: 306: Restore Always-Strict Floating-Point Semantics Message-ID: The following JEP with scope "SE" has been proposed to target JDK 17: 306: Restore Always-Strict Floating-Point Semantics https://openjdk.java.net/jeps/306 Summary: Make floating-point operations consistently strict, rather than have both strict floating-point semantics (strictfp) and subtly different default floating-point semantics. This will restore the original floating-point semantics to the language and VM, matching the semantics before the introduction of strict and default floating-point modes in Java SE 1.2. The announced deadline for feedback to jdk-dev is Fri 28 May 23:59 UTC: https://mail.openjdk.java.net/pipermail/jdk-dev/2021-May/005596.html If there are no unresolved objections at that time, then the JEP will be moved to the Targeted state, indicating that the feature is expected to appear in the specified release of the JDK Project. For more information about states, see the JEP Process document: https://openjdk.java.net/jeps/1 A dashboard that lists JEPs with "SE" scope may be found via a link on this page: https://openjdk.java.net/projects/jdk/17/spec/ Thanks, Iris From iris.clark at oracle.com Sat May 22 01:26:07 2021 From: iris.clark at oracle.com (Iris Clark) Date: Sat, 22 May 2021 01:26:07 +0000 Subject: JSR 392 (Java SE 17): JEP Proposed to Target: 411: Deprecate the Security Manager for Removal Message-ID: The following JEP with scope "SE" has been proposed to target JDK 17: 411: Deprecate the Security Manager for Removal https://openjdk.java.net/jeps/411 Summary: Deprecate the Security Manager for removal in a future release. The Security Manager dates from Java 1.0. It has not been the primary means of securing client-side Java code for many years, and it has rarely been used to secure server-side code. To move Java forward, we intend to deprecate the Security Manager for removal in concert with the legacy Applet API (JEP 398). The announced deadline for feedback to jdk-dev is Fri 28 May 23:59 UTC: https://mail.openjdk.java.net/pipermail/jdk-dev/2021-May/005595.html If there are no unresolved objections at that time, then the JEP will be moved to the Targeted state, indicating that the feature is expected to appear in the specified release of the JDK Project. For more information about states, see the JEP Process document: https://openjdk.java.net/jeps/1 A dashboard that lists JEPs with "SE" scope may be found via a link on this page: https://openjdk.java.net/projects/jdk/17/spec/ Thanks, Iris