Skip to content

Conversation

liach
Copy link
Member

@liach liach commented Sep 18, 2025

The Signature modeling in the ClassFile API is missing some validations required by JVMS, notably identifier character restrictions and void type restrictions. In addition, the model currently uses ClassDesc to indicate a simple name for an inner class signature, which is incorrect, and this patch proposes to deprecate that API for removal.


Progress

  • Change must be properly reviewed (1 review required, with at least 1 Reviewer)
  • Change must not contain extraneous whitespace
  • Commit message must refer to an issue
  • Change requires CSR request JDK-8368051 to be approved

Issues

  • JDK-8368050: Validation missing in ClassFile signature factories (Bug - P4)
  • JDK-8368051: Validation missing in ClassFile signature factories (CSR)

Reviewers

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/27380/head:pull/27380
$ git checkout pull/27380

Update a local copy of the PR:
$ git checkout pull/27380
$ git pull https://git.openjdk.org/jdk.git pull/27380/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 27380

View PR using the GUI difftool:
$ git pr show -t 27380

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/27380.diff

Using Webrev

Link to Webrev Comment

@bridgekeeper
Copy link

bridgekeeper bot commented Sep 19, 2025

👋 Welcome back liach! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

@openjdk
Copy link

openjdk bot commented Sep 19, 2025

@liach This change now passes all automated pre-integration checks.

ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details.

After integration, the commit message for the final commit will be:

8368050: Validation missing in ClassFile signature factories

Reviewed-by: asotona

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been 36 new commits pushed to the master branch:

As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.

➡️ To integrate this PR with the above commit message to the master branch, type /integrate in a new comment.

@openjdk openjdk bot added csr Pull request needs approved CSR before integration core-libs [email protected] labels Sep 19, 2025
@openjdk
Copy link

openjdk bot commented Sep 19, 2025

@liach The following label will be automatically applied to this pull request:

  • core-libs

When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command.

@openjdk openjdk bot added the rfr Pull request is ready for review label Sep 19, 2025
@mlbridge
Copy link

mlbridge bot commented Sep 19, 2025

Webrevs

* {@return a class type signature}
*
* @param outerType signature of the outer type, may be {@code null}
* to indicate this is a top-level class or interface
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually here is the ambiguity. Null outer type is more than frequently used also for inner classes.
Signatures of inner classes are mainly encoded without the outer type and with the $-notation of the outer$inner as the class name.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Clarified by introducing examples of signature strings and on the className/outerType.

*/
public static ClassTypeSig of(ClassTypeSig outerType, String className, TypeArg... typeArgs) {
requireNonNull(className);
return new SignaturesImpl.ClassTypeSigImpl(Optional.ofNullable(outerType), className.replace(".", "/"), List.of(typeArgs));
Copy link
Member

@asotona asotona Sep 19, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should declare that the method does not accept binary class names, If we remove the conversion.
And that seems to be a significant compatibility change.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, this spec links to "identifiers" which explicitly rejects dots. Added this risk in the CSR. I think we should be fine here.

Copy link
Member

@asotona asotona left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me.

@openjdk openjdk bot added ready Pull request is ready to be integrated and removed csr Pull request needs approved CSR before integration labels Sep 23, 2025
@liach
Copy link
Member Author

liach commented Sep 23, 2025

Thanks for the reviews!

/integrate

@openjdk
Copy link

openjdk bot commented Sep 23, 2025

Going to push as commit f9b91a7.
Since your change was applied there have been 50 commits pushed to the master branch:

Your commit was automatically rebased without conflicts.

@openjdk openjdk bot added the integrated Pull request has been integrated label Sep 23, 2025
@openjdk openjdk bot closed this Sep 23, 2025
@openjdk openjdk bot removed ready Pull request is ready to be integrated rfr Pull request is ready for review labels Sep 23, 2025
@openjdk
Copy link

openjdk bot commented Sep 23, 2025

@liach Pushed as commit f9b91a7.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core-libs [email protected] integrated Pull request has been integrated
Development

Successfully merging this pull request may close these issues.

2 participants