On Fri, 21 Feb 2025 09:30:05 GMT, Daniel Fuchs <dfu...@openjdk.org> wrote:
>> src/java.management/share/classes/javax/management/modelmbean/DescriptorSupport.java >> line 1170: >> >>> 1168: " with arg: <" + s + ">"; >>> 1169: throw new XMLParseException(e, msg); >>> 1170: // XMLParseException is deprecated for removal. >> >> Q: Non-deprecated method will be using the deprecated class >> `XMLParseException`. What is the plan for replacement? Should this be fixed >> now? The same question for the line 1160. > > Aside from the public deprecated API, the only places where this exception is > used is in private static methods that support the implementation of the > deprecated constructor, so these will go away when the constructor is > eventually removed. 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. ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/23038#discussion_r1965166254
