X hits on this document

69 views

0 shares

0 downloads

0 comments

13 / 20

Chapter 4. The RichFaces Migration Issues 3.1.x

  • -

    3.2.0

      • 4.2.5.

        Action listeners calling problem with <a4j:actionparam>

on JSP page

4.2.5.1. Description

As it has been mentioned above we've migrated to JSF 1.2 standard in RichFaces 3.2.0. The order of calling action listeners has been changed in JSF 1.2: first the listener of the component itself is called then the other listeners are called.

This is why the <a4j:actionparam> component setter is called after "actionListener" of the component itself. In the following example #{bean.action} is called before #{bean.value}:

Example:

... <a4:support actionListener="#{bean.action}" event="onclick">

<a4j:actionparam assignTo="#{bean.value}" value="John"/> </a4j:support> ...

This issue occurs in JSP pages only.

        • 4.2.5.2.

          Links

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

        • 4.2.5.3.

          How to reproduce

... <f:view>

<h:form> <h:panelGrid width="120" border="5">

<a4j:support event="onclick" reRender="rep" actionListener="#{actionPlanBean.actionListener}">

<a4j:actionparam name="username" value="John" assignTo="#{actionPlanBean.name}" /> </a4j:support> <h:outputLabel value="Panel 1 - John"/> </h:panelGrid> <rich:panel> <h:outputText id="rep" value="I say: #{actionPlanBean.helloLabel}"/> </rich:panel> </h:form>

14

Document info
Document views69
Page views69
Page last viewedWed Jan 18 02:42:07 UTC 2017
Pages20
Paragraphs460
Words3352

Comments