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

[Phil Race]

On Wed, 18 Jun 2025 17:57:26 GMT, Phil Race <prr at openjdk.org> wrote:

> Clarify the behaviour of new HeadlessException().getMessage()
> The spec. is updated to be clear that empty means null, not an empty string.

> > > 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
> 
> I see, thank you for your clarification.
> 
> So, this is a minimal update to the specification to quickly address the problem with `null` vs. _empty_ message, which is being backported to JDK 25; the specification for JDK 26 is going to be overhauled shortly.
> 
> Is my understanding correct now?

Right. What I am obliged to do in order to satisfy one specific TCK test. Nothing more.

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

PR Comment: https://git.openjdk.org/jdk/pull/25881#issuecomment-2988708586