RFR: 8358526: Clarify behavior of java.awt.HeadlessException constructed with no-args

[Phil Race]

On Wed, 18 Jun 2025 18:34:32 GMT, Alexey Ivanov <aivanov at openjdk.org> wrote:

> Should each constructor specify how the message returned by `getMessage` is constructed instead of _directing to the specification of `getMessage` for details_?

100% no. I am not wasting time on that. This whole spec. is getting revamped  again in JDK 26 in very short order after this minimal fix is backported to JDK 25

> src/java.desktop/share/classes/java/awt/HeadlessException.java line 56:
> 
>> 54:      * For such {@code HeadlessException} the default headless error message
>> 55:      * may be auto-generated for some platforms.
>> 56:      * The text of the default headless message may depend on
> 
> This doesn't align, the following text has to be modified too.
> 
> The first sentence of the second paragraph, “For such `{@code HeadlessException}` the default headless error message may be auto-generated for some platforms,” should be replaced with the slightly edited text from the `HeadlessException(String)` constructor: “For some platforms, the `{@code null}` detail message may be replaced with the default headless error message.”

I don't see why.

-------------

PR Comment: https://git.openjdk.org/jdk/pull/25881#issuecomment-2985884731
PR Review Comment: https://git.openjdk.org/jdk/pull/25881#discussion_r2155631076