Uploaded image for project: 'RichFaces'
  1. RichFaces
  2. RF-13455

The rich:tabPanel no longer visits tab header facets while rendering a response.

    Details

      Description

      I use ajax to update the header label of rich:tab. That is why label is placed in a header-facet. Since RF 4.3.4 this does not work:

      <?xml version="1.0" encoding="UTF-8"?>
      <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
        "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
      
      <html xmlns="http://www.w3.org/1999/xhtml" xmlns:ui="http://java.sun.com/jsf/facelets" xmlns:h="http://java.sun.com/jsf/html"
        xmlns:c="http://java.sun.com/jsp/jstl/core" xmlns:rich="http://richfaces.org/rich" xmlns:a4j="http://richfaces.org/a4j"
        xmlns:f="http://java.sun.com/jsf/core" xml:lang="en" lang="en">
      <h:head>
      </h:head>
      <h:body>
        
        <a4j:log hotkey="M" mode="popup" />
      
        <h:form id="form" prependId="false">
          <rich:tabPanel id="tabPanel">
            <rich:tab header="tab 1">
              <a4j:commandLink value="click me" action="#{testBean.put('clicks',testBean.clicks + 1)}" render="label" execute="@this" />
            </rich:tab>
            <rich:tab>
              <f:facet name="header">
                <h:outputText id="label" value="#{testBean.clicks} clicks" />
              </f:facet>
            </rich:tab>
          </rich:tabPanel>
        </h:form>
      
      </h:body>
      </html>
      

      testBean is a simple session-scoped HashMap.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  bleathem Brian Leathem
                  Reporter:
                  alsha Alexey Shakov
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Time Tracking

                    Estimated:
                    Original Estimate - 2 hours
                    2h
                    Remaining:
                    Remaining Estimate - 2 hours
                    2h
                    Logged:
                    Time Spent - Not Specified
                    Not Specified