Skip to content
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

Fixed #6375 XmlConfiguration always checks for setter method #6398

Merged
merged 4 commits into from Jun 15, 2021

Conversation

gregw
Copy link
Contributor

@gregw gregw commented Jun 11, 2021

Fix #6375 by making XmlConfiguration Set handling always check for a matching setter, even if the property attribute is given but not set.

Signed-off-by: Greg Wilkins gregw@webtide.com

Fix #6375 by making XmlConfiguration Set handling always check for a matching setter, even if the property attribute is given but not set.

Signed-off-by: Greg Wilkins <gregw@webtide.com>
@gregw gregw added this to In progress in Jetty 10.0.6/11.0.6 FROZEN via automation Jun 11, 2021
@gregw gregw requested a review from janbartel June 11, 2021 05:30
Jetty 10.0.6/11.0.6 FROZEN automation moved this from In progress to Review in progress Jun 11, 2021
Also check for public fields

Signed-off-by: Greg Wilkins <gregw@webtide.com>
@gregw gregw requested a review from janbartel June 11, 2021 07:43
Copy link
Contributor

@janbartel janbartel left a comment

Choose a reason for hiding this comment

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

LGTM

Jetty 10.0.6/11.0.6 FROZEN automation moved this from Review in progress to Reviewer approved Jun 14, 2021
@gregw gregw merged commit a492473 into jetty-10.0.x Jun 15, 2021
Jetty 10.0.6/11.0.6 FROZEN automation moved this from Reviewer approved to Done Jun 15, 2021
@gregw gregw deleted the jetty-10.0.x-6375-xmlSetWithWrongName branch June 15, 2021 03:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Development

Successfully merging this pull request may close these issues.

Always check XML Set elements with property attribute
2 participants