On Sun, 23 Feb 2025 20:58:08 GMT, Kevin Walls <kev...@openjdk.org> wrote:
>> But the question is interesting. There could be code out there that >> instantiate and throws this exception for its own purpose. Or that tries to >> catch it, or instanceof it... Maybe we should let it linger longer than the >> associated API that throws it. > > If we wanted to be really cautious, we could hold off removal of the > exception class. But we should still deprecate it for removal now. > Code out there using specifically > javax/management/modelmbean/XMLParseException would most likely be a mistake, > it most likely meant some other XMLParseException class... There really > should not be any external usage... OK ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/23038#discussion_r1967559781
