-
Notifications
You must be signed in to change notification settings - Fork 6.1k
8357598: Toolkit.removeAWTEventListener should handle null listener in AWTEventListenerProxy #25401
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…n AWTEventListenerProxy
👋 Welcome back serb! A progress list of the required criteria for merging this PR into |
@mrserb 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:
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 104 new commits pushed to the
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 |
System.out.println("Do not test for XAWT Toolkit."); | ||
System.out.println("Passing automatically."); | ||
return; | ||
} | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I do not know why it was disabled on XToolkit, seems to work fine.
Webrevs
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good.
I'll submit a test job.
test/jdk/java/awt/Toolkit/AWTEventListenerProxyTest/AWTEventListenerProxyTest.java
Outdated
Show resolved
Hide resolved
…stenerProxyTest.java Co-authored-by: Alexey Ivanov <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Ran a test job myself and everything looks good.
private static void verify(Toolkit tk, int expected) { | ||
AWTEventListener[] array = tk.getAWTEventListeners(); | ||
if (array == null || array.length != expected) { | ||
System.out.println("[Simple test failed!!]"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think this print statement is required?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably not, but it follows the common pattern in the test.
@@ -23,7 +23,7 @@ | |||
|
|||
/* |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/* | |
/* | |
* @test | |
* @bug 4290704 8357598 | |
* @summary Test use of AWTEventListenerProxyTest class | |
*/ |
Most of the test follow this pattern for jtreg tags. It would be good if you use it too for code consistency.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not required, but can be updated…
/integrate |
Going to push as commit 3a3ea7e.
Your commit was automatically rebased without conflicts. |
The issue was found here: #24692 (comment)
AWTEventListener and AWTEventListenerProxy are public classes and there's no assertion that EventListenerProxy.getListener() will always return a non-null value. So removeAWTEventListener method should fetch the listener from the proxy and check it for null similar to how it is implemented in addAWTEventListener. Currently, it works fine because we never insert null values into the map. So it is just a code clarification.
One of the test is updated just to touch that codepath.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/25401/head:pull/25401
$ git checkout pull/25401
Update a local copy of the PR:
$ git checkout pull/25401
$ git pull https://git.openjdk.org/jdk.git pull/25401/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 25401
View PR using the GUI difftool:
$ git pr show -t 25401
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/25401.diff
Using Webrev
Link to Webrev Comment