rootvector2 opened a new pull request, #428: URL: https://github.com/apache/commons-beanutils/pull/428
Port of #426 to 1.X. `set` passes the raw lower-cased property name to `ResultSet.updateObject` while the read path resolves it through `getColumnName` first, so under the default `lowerCase` an update to a mixed-case column targets the wrong column or throws on a case-sensitive driver. Same one-line fix and regression test as master, with the test adapted to the JUnit 3 style on this branch (and using `AtomicReference` per the review on #426). `DynaResultSetTest.testSetUsesColumnName` fails on clean `1.X` with `expected:<string[P]roperty> but was:<string[p]roperty>` and passes with the change. Note: as on #417, `mvn` on a clean `1.X` checkout fails `LocaleBeanificationTest#testContextClassloaderIndependence` in my environment (it passes in isolation), so no fully green default-goal run locally; the failure is identical with and without this change. `apache-rat:check` and `checkstyle:check` pass. - [x] Read the [contribution guidelines](CONTRIBUTING.md) for this project. - [ ] Read the [ASF Generative Tooling Guidance](https://www.apache.org/legal/generative-tooling.html) if you use Artificial Intelligence (AI). - [ ] I used AI to create any part of, or all of, this pull request. Which AI tool was used to create this pull request, and to what extent did it contribute? - [ ] Run a successful build using the default [Maven](https://maven.apache.org/) goal with `mvn`; that's `mvn` on the command line by itself. - [x] Write unit tests that match behavioral changes, where the tests fail if the changes to the runtime are not applied. This may not always be possible, but it is a best practice. - [x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why. - [x] Each commit in the pull request should have a meaningful subject line and body. Note that a maintainer may squash commits during the merge process. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
