-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8349516: StAXStream2SAX.handleCharacters() fails on empty CDATA #23847
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
|
👋 Welcome back joehw! A progress list of the required criteria for merging this PR into |
|
@JoeWang-Java 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 33 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 |
|
@JoeWang-Java The following label will be automatically applied to this pull request:
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. |
Webrevs
|
| if (textLength > 0) { | ||
| staxStreamReader.getTextCharacters(0, chars, 0, textLength); | ||
| } |
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.
Hi Joe,
The comment above this piece reads:
// workaround for bugid 5046319 - switch over to commented section
// below when it is fixed.
And the bug 5046319 (closed issue about AIOOBE) is fixed. Should the commented section be considered?
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.
Hi Naoto,
Yes, I did look through that code and bug 5046319. Unfortunately, it happened when JAXP was standalone, the history of the change was lost.
The variable "buf" seems to be an instance variable that serves to cache the text read. That part had been changed as well. Furthermore, if buf starts with zero length, the call to getTextCharacters would still result in IndexOutOfBoundsException.
Maybe the commented code can be removed, I kept them as is in case they may be useful reference as a history.
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.
OK, then I'd suggest removing the above comment and commented section altogether, as it only provides confusion.
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.
Yeah, agree. The code is stable as is.
| * @throws Exception if the test fails, in which case the parser throws | ||
| * IndexOutOfBoundsException. |
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.
Do we need this throws Exception clause (and the method declaration below)? Since AIOOBE is a RuntimeException, this throws clause does not seem to be necessary. Simple description of the failure case may suffice.
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.
Thanks Naoto. Improved the javadoc a bit.
naotoj
left a comment
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. Thanks for the update
|
/integrate |
|
Going to push as commit 96613cc.
Your commit was automatically rebased without conflicts. |
|
@JoeWang-Java Pushed as commit 96613cc. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Fix handleCharacters by adding a guard to zero length and letting the rest of the process continue (e.g. closing tags and etc).
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/23847/head:pull/23847$ git checkout pull/23847Update a local copy of the PR:
$ git checkout pull/23847$ git pull https://git.openjdk.org/jdk.git pull/23847/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 23847View PR using the GUI difftool:
$ git pr show -t 23847Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/23847.diff
Using Webrev
Link to Webrev Comment