X hits on this document

86 views

0 shares

0 downloads

0 comments

14 / 20

Chapter 4. The RichFaces Migration Issues 3.1.x

  • -

    3.2.0

</f:view> ...

4.2.5.4. Causes

Please, see Jira [http://jira.jboss.com/jira/browse/RF-3080].

4.2.5.5. Workarounds

The solution is to use <a4j:actionParam> before:

... <f:actionListener binding="#{skin.binding}"/> ...

      • 4.2.6.

        Behavior of the "immediate" attribute is changed

        • 4.2.6.1.

          Description

Since we've migrated to the JSF 1.2 standard in RichFaces 3.2.0 the "immediate" attribute works exactly like it should according to the JSF 1.2 specification: the default ActionListener stops execution after the Apply Request Values phase, so there is no interaction with a model any more.

We could not use the standard JSF API before as soon as we had to support not only JSF 1.2, but JSF 1.1 as well. We used our own hack that emulated the behavior of the attribute. This approach had a side effect that allowed interacting with a model but now this side effect is gone.

        • 4.2.6.2.

          Links

          • RichFaces Forum [http://www.jboss.com/index.html?module=bb&op=viewtopic&t=133031]

        • 4.2.6.3.

          How to reproduce

... <h:form> <h:inputText id="oneA" value="#{bean.name}" size="8">

<a4j:supp event="onkeyureRender="threimmediate="trufocus="oneaction="#{bean.actionOne}"/ >

</h:inputText> <h:selectBooleanCheckbox id="twoA" value="#{bean.option}">

<a4j:suppoevent="onclicreRender="threimmediate="trufocus="twoaction="#{bean.actionOne}"/ >

15

Document info
Document views86
Page views86
Page last viewedMon Jan 23 17:26:05 UTC 2017
Pages20
Paragraphs460
Words3352

Comments