volosied commented on PR #607:
URL: https://github.com/apache/myfaces/pull/607#issuecomment-1769148959
I'm not able to reproduce this outside the app. Perhaps you could take a
look? I can't create another custom component like p:calendar to replicate
this problem with. @tandraschko
However. c:forEach is broken and we've had many issues in the past. I'm
not too happy with this fix, but, given the state of things with c:forEach, I
think we should merge this it.
Leo also mentioned
[here](https://github.com/apache/myfaces/blob/50d6e0ec3507f0b5d8c2b7492505ac683180b9a0/impl/src/main/java/org/apache/myfaces/view/facelets/PartialStateManagementStrategy.java#L604C1-L606C72):
// By effect of c:forEach it is possible that the
component can be duplicated
// in the component tree, so what we need to do as a
fallback is replace the
// component in the spot with the restored version.
It seems to me that this very rare scenario with Resource Dependencies was
overlooked?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
