Adjust spec to state that #{cc} must be resolved using EL instead of CDI #2003
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
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.
Moving #{cc} resolution from EL to CDI during Faces 4.0 was a mistake. This primarily because within a single EL resolution, the #{cc} can refer different composite components depending on the nesting level and whether a nested one references the attribute of a parent one. This worked with Weld because it re-resolved the #{cc} on every access, but not with OWB because it caches the result for the duration of the single EL resolution. This ultimately caused an infinite loop when attempting to reference the #{cc} of the parent composite. There's nothing in CDI spec which forbids OWB's behavior.
Related issue ticket: #1564 (comment)
Mojarra impl fix: eclipse-ee4j/mojarra#5549