rzo1 opened a new pull request, #173: URL: https://github.com/apache/openjpa/pull/173
To answer the review question: 3.2 did not change property-name resolution — the test was adapting to a regression this PR introduced. `d488eab97` required an upper-case character after the `get`/`is`/`set` prefix, which made the JavaBeans-style `getaWord()`/`setaWord()`/`isaBoolean()` accessors stop being accessors: the property vanished with no error and no warning, and the next day the test entity was renamed to make the test green. `68671e667`, titled "Support lowercase property names after get/set prefix", already took that requirement off `isNormalGetter` and `isSetter`, but missed the identical one in `isBooleanGetter`. This removes it there too, so all three agree. No property or column names change: OpenJPA lower-cases the first character after the prefix unconditionally — deliberately unlike `Introspector.decapitalize` — so `getaWord()` and `getAWord()` have always resolved to the same property. What changes is only that an entity whose boolean property is spelled `isaXxx()` is recognised again, as it was in 4.1.x. `PropertyAccessCapitalization` goes back to the spelling it was written for, so it and `PropertyAccessCapitalizationOldBehavior` once more cover the two spellings instead of the same one twice. `TestAccessorNameDerivation` pins the rule itself, without needing a database. -- 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]
