Reject competing read and write accessors for PropertyAccessor and IndexAccessor in SpEL
#32737
Assignees
Labels
in: core
Issues in core modules (aop, beans, core, context, expression)
type: enhancement
A general enhancement
Milestone
Comments
sbrannen
added
in: core
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Overview
While working on #26478 and related issues, it became apparent that a developer can inadvertently register one
PropertyAccessorfor reading a given property and a second competing accessor for writing the same property, which can lead to improper behavior when a cached accessor is expected to be able to support both read and write access for a given property.The same can happen with multiple competing
IndexAccessorimplementations.We have therefore decided to reject competing read and write accessors for the same property or the same index for both
PropertyAccessorandIndexAccessor, respectively, starting with Spring Framework 6.2.Related Issues
IndexAccessorSPI to customize the SpELIndexer#26478The text was updated successfully, but these errors were encountered: