On Tue, 1 Aug 2023 03:46:31 GMT, Sergey Bylokhov <s...@openjdk.org> wrote:
> It was left there since the JFormattedTextField class is Serializable, and it > is a kind of "public" API because it is mentioned in the serializable form of > this class(I think so). See an example where I had to add the spec to the > private fields via CSR: https://bugs.openjdk.org/browse/JDK-8252544 > > But the JFormattedTextField is part of the Swing where we intentionally added > a statement "Serialized objects of this class will not be compatible with > future Swing releases" So we can delete it but probably CSR will be needed, I > am not sure. None of the Swing components is present in the [Serialized Form](https://docs.oracle.com/en/java/javase/17/docs/api/serialized-form.html) for Java 17. However, the field is still part of a serialized object. If a CSR is required, it may not be worth the effort. ------------- PR Comment: https://git.openjdk.org/jdk/pull/15088#issuecomment-1660029391
