Maxim Solodovnik created OPENJPA-2993:
-----------------------------------------
Summary: Renamed getaXxx accessors drop JavaBeans naming coverage
Key: OPENJPA-2993
URL: https://issues.apache.org/jira/browse/OPENJPA-2993
Project: OpenJPA
Issue Type: Sub-task
Components: jpa
Affects Versions: 4.2.0
Reporter: Maxim Solodovnik
Fix For: 4.2.0
Discussion thread:
https://github.com/apache/openjpa/pull/144#discussion_r3683007048
**(medium)** The accessors were renamed from the JavaBeans-Introspector style
(getaCAPITAL/getaWord/isaBoolean for fields aCAPITAL/aWord/aBoolean) to
getACAPITAL/getAWord/isABoolean. This test existed precisely to cover the
former naming, so property-access entities using IDE-generated getaXxx
accessors would silently stop being recognized. Did 3.2 change property-name
resolution, or is this adapting the test to a regression? Could both variants
stay covered?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
