Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use ELContext instead of deprecated VariableResolver API in JspPropertyAccessor #32383

Closed
sbrannen opened this issue Mar 6, 2024 · 0 comments
Assignees
Labels
in: web Issues in web modules (web, webmvc, webflux, websocket) type: enhancement A general enhancement
Milestone

Comments

@sbrannen
Copy link
Member

sbrannen commented Mar 6, 2024

The JSP VariableResolver API has been deprecated since JSP 2.1 in favor of the newer ELContext API.

We should therefore use ELContext instead of the deprecated VariableResolver API in JspPropertyAccessor.

@sbrannen sbrannen added in: web Issues in web modules (web, webmvc, webflux, websocket) type: enhancement A general enhancement labels Mar 6, 2024
@sbrannen sbrannen added this to the 6.2.0-M1 milestone Mar 6, 2024
@sbrannen sbrannen self-assigned this Mar 6, 2024
sbrannen pushed a commit that referenced this issue Dec 14, 2024
Prior to this commit, the order of parameters passed to
ELResolver#getValue was incorrect.

The `name` should correspond to the `property` parameter of the
`getValue` method instead the `base` parameter.

See gh-32383
See gh-33942
Closes gh-33945
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: web Issues in web modules (web, webmvc, webflux, websocket) type: enhancement A general enhancement
Projects
None yet
Development

No branches or pull requests

1 participant