[richfaces-issues] [JBoss JIRA] (RF-12548) rich:tabPanel does not work after ajax request

Marco Goetz (JIRA) jira-events at lists.jboss.org
Mon Oct 22 08:20:01 EDT 2012


Marco Goetz created RF-12548:
--------------------------------

             Summary: rich:tabPanel does not work after ajax request
                 Key: RF-12548
                 URL: https://issues.jboss.org/browse/RF-12548
             Project: RichFaces
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: component-output
    Affects Versions: 4.2.3.Final
            Reporter: Marco Goetz
             Fix For: 4.2.4




I have a strange problem with the rich:tabPanel in combination with an ajax request and a commandLink.
After clicking the a4j:commandLink "Update" Button the rich:tabPanel is not switching anymore.
 
The browser's console log says:
new RichFaces.ui.TabPanel("j_id_5:panel1", ({ajax:{incId:"1"}, activeItem:"j_id_9", isKeepHeight:false, cycledSwitching:false})) is not a function
at jsf.js.jsf:3682
 
Example Code:
<h:head>
</h:head>
<body>
          <h:form>
                    <a4j:commandLink value="Update" action="#{testBean.update}" render="contentDiv" />
 
                    <t:div id="contentDiv">
                              <rich:tabPanel switchType="client" id="panel1">
 
                                        <rich:tab>
                                                  Tab1
                                                  <h:commandLink action="#{test.testAction}" />
                                        </rich:tab>
 
                                        <rich:tab>
                                                  Tab2
                                        </rich:tab>
 
                              </rich:tabPanel>
                    </t:div>
          </h:form>
</body>
 
The very strange thing is when I remove the the h:commandLink in Tab1 the switching works fine after the ajax request.
When I change the render attribute to "@all" it works too, but that would be a bad workaround.

I use MyFaces 2.1.8 and Richfaces 4.3.0.M1. 
Prolem stil exists with Richfaces 4.3.2.Final.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the richfaces-issues mailing list