X hits on this document

55 views

0 shares

0 downloads

0 comments

11 / 20

Chapter 4. The RichFaces Migration Issues 3.1.x

  • -

    3.2.0

one <rich:datascroller> component. It is a common pattern to have 2 <rich:datascroller> components: the first in the header, the second in the footer. In this case the first one will not work.

4.2.2.2. Links

  • Jira [http://jira.jboss.com/jira/browse/RF-2970]

  • RichFaces

Forum

[http://www.jboss.com/index.html?

module=bb&op=viewtopic&p=4141786#4141786]

4.2.2.3. How to reproduce

The described above problem occurs if two <rich:datascroller> components are added to any table.

4.2.2.4. Causes

The <rich:datascroller> component does not manage the scroll state of a data table.

4.2.2.5. Workarounds

The solution is to use "page" attribute and bind it to the same property for all <rich:datascroller> components.

      • 4.2.3.

        Static "for" attribute in <rich:datascroller>

        • 4.2.3.1.

          Description

The "for"attribute of <rich:datascroller> component doesn't allow EL expressions in 3.2.0.GA.

Custom tags exploiting the ability of the <rich:datascroller> to have dynamic "for" attribute doesn't work.

4.2.3.2. Links

  • Jira [http://jira.jboss.com/jira/browse/RF-2923]

        • 4.2.3.3.

          How to reproduce

The described above problem occurs if the following code is used:

... <rich:datascroller for="#{bean.property}"/> ...

12

Document info
Document views55
Page views55
Page last viewedSun Dec 04 14:40:47 UTC 2016
Pages20
Paragraphs460
Words3352

Comments