Use of JCP site is subject to the
JCP Terms of Use and the
Oracle Privacy Policy
|
JSR 384 Maintenance Release 1: Java SE 11
Change Summary
This document describes additional changes to the specification of JSR 384 which is defined by the Final Release in September 2018. When specification text is provided, insertions are shown on a light green background and deletions are shown struck through on a light red background. Send comments to java-se-mr-spec-comments@openjdk.java.net. 1
There is no change to the values returned by the system
properties 2
Eras in the Japanese imperial calendar are tied to the reign of the
emperor. On 1 May 2019, a new era will be introduced with the ascension of
the new emperor. The specification of
The Change Specification Request (CSR) associated with this change is 8215946. 3
In the Java SE Platform, support for the Unicode Standard is vested
mainly in the
Additionally, minor corrections were made to the following method descriptions:
The CSR associated with this change is 8216594. 4
As industry-wide cryptographic standards evolve, the set of algorithms and
protocols supported by the security APIs needs to change. The
Java Security Standard Algorithm Names specification defines the set of
String names referencing these standards (e.g. The Java SE Security API requires and uses a set of standard names for algorithms, certificate and keystore types. This specification establishes the following names as standard names. Note that an SE implementation may support additional algorithms that are not defined in this specification. As a best practice, if an algorithm is defined in a subsequent version of this specification and an implementation of an earlier specification supports that algorithm, the implementation should use the standard name of the algorithm that is defined in the subsequent specification. Each SE implementation should also document the algorithms that it supports or adds support for in subsequent update releases. The algorithms may be documented in release notes or in a separate document such as the JDK Security Providers document. In some cases naming conventions are given for
forming names that are not explicitly listed, to facilitate name consistency
across provider implementations. Items in angle brackets (such
as Note: Standard names are not case-sensitive. The CSR associated with this change is 8215320. |