UIRepeat et al are not specified
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 127
- Forks
- 59
- Avg merge
- 23h
- Merged PRs (30d)
- 7
Description
with JSF 2.0, thanks to Facelets, there is a . While I understand
that tags/rendering behavior is part of the internals of an implementation, I am
not really sure if the underlying/related components should be "hidden" by the
spec as well.
For instance: I noticed that in MyFaces the UIRepeat extends UIComponentBase and
implements NamingContainer, while with the JSF RI / Mojarra, the UIRepeat "just"
extends the UINamingContainer...
... and oh yes... I know that UINamingContainer extends UIComponentBase and
implements NamingContainer....
but instanceof UINamingContainer doesn't say TRUE for the MyFaces UIRepeat
See a community related discussion here:
[http://markmail.org/message/wllfudu4ge7n5gxa](http://markmail.org/message/wllfudu4ge7n5gxa)
#### Environment
Operating System: All
Platform: All
#### Affected Versions
[2.0]
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the issue's comparison of MyFaces and Mojarra UIRepeat, including UIComponentBase, UINamingContainer, and NamingContainer, then read the linked community discussion. Determine whether the Jakarta Faces specification should define the related component type or inheritance behavior, and document a resolution that addresses the cross-implementation difference.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100