Improve exception message for failed property access in SpEL [SPR-11535] #16160
Labels
in: core
Issues in core modules (aop, beans, core, context, expression)
status: backported
An issue that has been backported to maintenance branches
type: enhancement
A general enhancement
Milestone
Oliver Drotbohm opened SPR-11535 and commented
In case property access for a bean property fails, SpEL's
PropertyOrFieldReference
currently throws an exception with the following message:As
PropertyOrFieldReference
is only looking for public fields, it would be nice if that was reflected in the error message as one might be puzzled if the field actually exists but is not a public one.Affects: 3.2.8, 4.0.2
Referenced from: commits 27cacf0, eeb82c4
Backported to: 3.2.9
The text was updated successfully, but these errors were encountered: