Prevent ScopedAttributeELResolver to create Session/ViewScope as a si… #4448
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
arjantijms
approved these changes
Aug 22, 2018
…de-effect (by calling getValue/setValue) Signed-off-by: Xavier DURY <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix for #3943 (previously known as JAVASERVERFACES-3939).
When calling
setValue(...)orgetValue(...)onScopedAttributeELResolver, those methods do not check if a session exists before callingExternalContext.getSessionMap()or if a view-scope exists before callingUIViewRoot.getViewMap(). This could mean that a superfluous session could be created or that a view-scope could be created in a transient view (and produce some confusing warnings in the logs).I know this issue has already been closed (for the wrong reason in my opinion) but I would like it to be re-examined.