I have achieved a partial compilation of the core caching logic for configServerJMXClient under Java 21. However, restoring its full web-services capability carries severe technical and operational risks.
Because this library was recovered entirely via disassembly from the Java 5/6 era, I strongly recommend we pause this migration and re-evaluate the initiative based on the following critical blind spots:
Key Risks & Technical Realities
Zero Test Safety Net: There are no unit or integration tests available for this codebase. Modifying low-level web-service plumbing to satisfy Java 21 rules will be done blindly, making undetected runtime regressions highly probable.
Missing Source Specifications & WSDLs: We do not possess the upstream .wsdl definitions. A dozen tightly coupled classes had to be disabled just to pass compilation. Attempting to manually refactor or reverse-engineer these decompiled stubs introduces unpredictable engineering friction with no documentation to validate the changes against.
Vanished Runtime APIs: Java 11+ completely removed the legacy enterprise modules (JAX-WS/JAXB) and internal APIs (com.sun.xml.internal.*) this library relies on. Forcing it to run requires complex build-toolchain overrides that introduce long-term technical debt.
Proceeding with the current port represents an unpredictable investment with high regression risks. Let's schedule a brief meeting to align on these findings.
Top comments (0)