There were a few other holes in the recent migration of BytecodeDescriptor, most notably:
1. BytecodeDescriptor is missing checks for `.`, `[` characters, leading, trailing, consecutive `/`, or empty name. 2. EnclosingMethod is only validated by hotspot to carry either field or method type. We still need to check for field types I have written up the behavioral changes in the CSR. In addition, I have added a few more tests to ensure the failure case behaviors of the migrated use sites. ------------- Commit messages: - Desc parse migration problems Changes: https://git.openjdk.org/jdk/pull/28079/files Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=28079&range=00 Issue: https://bugs.openjdk.org/browse/JDK-8370976 Stats: 152 lines in 7 files changed: 115 ins; 15 del; 22 mod Patch: https://git.openjdk.org/jdk/pull/28079.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/28079/head:pull/28079 PR: https://git.openjdk.org/jdk/pull/28079
