You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A PropertyOrFieldReference caches the PropertyAccessor used for the first evaluation of the node. However, if a new EvaluationContext is provided and a completely different set of PropertyAccessor instances is used, none of them actually ever get considered.
The test case below uses a custom PropertyAccessor that holds a Map of values. The second part of the test registers a new instance of it with different values and still the evaluation returns the old value.
Oliver Drotbohm opened SPR-15769 and commented
A
PropertyOrFieldReference
caches thePropertyAccessor
used for the first evaluation of the node. However, if a newEvaluationContext
is provided and a completely different set ofPropertyAccessor
instances is used, none of them actually ever get considered.The test case below uses a custom
PropertyAccessor
that holds aMap
of values. The second part of the test registers a new instance of it with different values and still the evaluation returns the old value.Affects: 4.3.9, 5.0 RC2
Issue Links:
Referenced from: commits bcf9f21, bffcd33
The text was updated successfully, but these errors were encountered: