We're updating the issue view to help you get more done. 

Problem finding correlated getter-method for field access

Description

introduced a potential bug that occurs whenever the persistent field has both a corresponding is and corresponding get method. E.g., given:

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 @Entity class MyEntity @Id Integer id; @Basic String someValue; ... String getSomeValue() { ... } boolean isSomeValue() { ... } }

The fix for attempted to reuse the code that is used to resolve the getter method for property-access, in which case it is illegal for there to be both. That is not the case here however.

Environment

None

Status

Assignee

Steve Ebersole

Reporter

Steve Ebersole

Fix versions

Labels

None

backPortable

None

Suitable for new contributors

None

Requires Release Note

None

Pull Request

None

backportDecision

None

Priority

Major