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

PropertyOrFieldReference suffers from potential NullPointerException [SPR-11031] #15659

Closed
spring-issuemaster opened this issue Oct 25, 2013 · 1 comment
Assignees
Milestone

Comments

@spring-issuemaster
Copy link
Collaborator

@spring-issuemaster spring-issuemaster commented Oct 25, 2013

Oliver Drotbohm opened SPR-11031 and commented

PropertyOrFieldReference.getValue(…) accesses ExpressionState.getConfiguration() without a check for null. If you've set up the ExpressionState with an EvaluationContext only, the configuration will be null.

Generally, ExpressionState could have a final configuration, default it to the default config used in SpelExpressionParser and let the constructors delegate to each other to avoid missing an assignment.


Affects: 3.2.4

Issue Links:

  • #14385 Support for increment (++) operator in SpEL
  • DATAMONGO-787 Guard against SpEL issue in Spring 3.2.4
@spring-issuemaster

This comment has been minimized.

Copy link
Collaborator Author

@spring-issuemaster spring-issuemaster commented Oct 25, 2013

Juergen Hoeller commented

Fixed through exposing a default SpelParserConfiguration in ExpressionState.

Juergen

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.