RichFaces
  1. RichFaces
  2. RF-11382

Datatable and ExtendedDatatable evaluate value attribute even if rendered=false

    Details

    • Type: Bug Bug
    • Status: Closed Closed (View Workflow)
    • Priority: Major Major
    • Resolution: Done
    • Affects Version/s: 4.0.0.Final, 4.1.0.Milestone2
    • Fix Version/s: 4.3.0.M3
    • Component/s: component-tables
    • Security Level: Public (Everyone can see)
    • Labels:
    • Environment:
      Fedora 15, Glassfish 3.1.1, CDI (Weld)
    • Bugzilla Update:
      Perform
    • Similar Issues:
      Show 10 results 

      Description

      In Richfaces 4 both datatable and extendedDatatable evaluate the value attribute even when rendered is set to false, even though it is not necessary. This makes it hard to achieve performance by trimming parts of the view tree. The built-in h:dataTable behaves correctly in that case.

      To reproduce simply try this snipplet:

      <h:form>
           <rich:dataTable value="#{myBean.property}" rendered="false">
            </rich:dataTable>
      </h:form>
      

      Side note: The reason I'm posting this is, that i want to embed a rich:dataTable in a ajax loaded rich:togglePanelItem which is loaded on demand. Probably fixing the "render" problem will also make the dataTable lazy-loadable when switching to the corresponding togglePanelItem.

      I hope this is no duplicate, I only found RichFaces 3 issues mentioning this problem.

        Issue Links

          Activity

          Hide
          RH Bugzilla Integration
          added a comment -

          Karel Piwko <kpiwko@redhat.com> changed the Status of bug 916314 from VERIFIED to CLOSED

          Show
          RH Bugzilla Integration
          added a comment - Karel Piwko <kpiwko@redhat.com> changed the Status of bug 916314 from VERIFIED to CLOSED
          Hide
          RH Bugzilla Integration
          added a comment -

          Karel Piwko <kpiwko@redhat.com> made a comment on bug 916314

          Closed as CURRENTRELEASE, part of WFK 2.2.0 distributables.

          Show
          RH Bugzilla Integration
          added a comment - Karel Piwko <kpiwko@redhat.com> made a comment on bug 916314 Closed as CURRENTRELEASE, part of WFK 2.2.0 distributables.
          Hide
          RH Bugzilla Integration
          added a comment -

          Marek Schmidt <maschmid@redhat.com> changed the Status of bug 916313 from RELEASE_PENDING to CLOSED

          Show
          RH Bugzilla Integration
          added a comment - Marek Schmidt <maschmid@redhat.com> changed the Status of bug 916313 from RELEASE_PENDING to CLOSED
          Hide
          Andrey Zhemoytuk
          added a comment -

          Still the issue is reproducible on postback (at least when partial state saving is turned off).

          Tried with RichFaces 4.3.3.Final and JSF 2.1.24 the following example:

            <h:form>
              <rich:dataTable rendered="false" value="#{viewScope.put('invoked', true)}">
              </rich:dataTable>
          
              <a4j:commandButton value="Postback" execute="@this" render="result"/>
            </h:form>
            
            <h:panelGroup id="result">
              #{invoked}
            </h:panelGroup>
          
          Show
          Andrey Zhemoytuk
          added a comment - Still the issue is reproducible on postback (at least when partial state saving is turned off). Tried with RichFaces 4.3.3.Final and JSF 2.1.24 the following example: <h:form> <rich:dataTable rendered= "false" value= "#{viewScope.put('invoked', true)}" > </rich:dataTable> <a4j:commandButton value= "Postback" execute= "@this" render= "result" /> </h:form> <h:panelGroup id= "result" > #{invoked} </h:panelGroup>
          Hide
          Brian Leathem
          added a comment -

          Andrey Zhemoytuk can you file a new issue for the partial state saving = false use case?

          Show
          Brian Leathem
          added a comment - Andrey Zhemoytuk can you file a new issue for the partial state saving = false use case?

            People

            • Assignee:
              Brian Leathem
              Reporter:
              Frederick Kämpfer
            • Votes:
              6 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

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

                  Agile