[richfaces-issues] [JBoss JIRA] (RF-12029) AbstractTogglePanel should extend UIRepeat, instead of UIOutput
[
https://issues.jboss.org/browse/RF-12029?page=com.atlassian.jira.plugin.s...
]
Brian Leathem commented on RF-12029:
------------------------------------
The TogglePanelRenderer#doDecode method calls the TabPanelRenderer#isSubmitted method
before adding the panel renderId to the PartialViewContext#renderIds.
On the first tab submit, TabPanelRenderer#isSubmitted returns false, because the call:
{code:title=TabPanelRenderer, line:90}
panel.getItem(panel.getSubmittedActiveItem())
{code}
Does not return a panel item that corresponds to the parameter.
The method/visitor that retrieves the tab panels by number needs to be looked at more
closely, and corrected.
AbstractTogglePanel should extend UIRepeat, instead of UIOutput
---------------------------------------------------------------
Key: RF-12029
URL: https://issues.jboss.org/browse/RF-12029
Project: RichFaces
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: component-output
Reporter: Brian Leathem
Assignee: Bernard Labno
Valid uses exist for dynamically generating rich:tab, rich:togglePanelItem,
rich:accordionItem. Current techniques for supporting this use case involve using
c:forEach, which is a problem since c: tags are processed too early to nicely support
dynamic use cases.
One idea to support this use case, is to have AbstractTogglePanel extend UIRepeat,
instead of UIOutput to better dynamic child components.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira