Mailing-List: contact users-help@myfaces.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "MyFaces Discussion" <users@myfaces.apache.org>
Received-SPF: pass (nike.apache.org: domain of andrew.rw.robinson@gmail.com
 designates 209.85.200.172 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=tvI8sloqNTPqeVqqNT5hVwvxXAv6ynk6hW2yFxlOs1Ss1BqG74JPnGAH3Hy1lDaJZvY7tAggOfo76HEHV2sy5of8RZ2MZviIDrnuJRWSyeWj+6w5BwHc5P/fnnCoaJvCRBJKqr6d6UQkfL+g7hwrQ2J60BLu1Fplv5tGpahxVNk=
Message-ID: <bc36a6210804151547n27982976t80ad638372e1ad8e@mail.gmail.com>
Date: Tue, 15 Apr 2008 16:47:36 -0600
From: "Andrew Robinson" <andrew.rw.robinson@gmail.com>
To: "MyFaces Discussion" <users@myfaces.apache.org>
Subject: Re: [Trinidad] setActionListener before actionListener or
 partialSubmit with action
In-Reply-To: <007601c89f49$c4493460$14b2a8c0@matzenote>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <bc36a6210804151533pe1ba3d9qf18605140e5e1283@mail.gmail.com>
	 <007601c89f49$c4493460$14b2a8c0@matzenote>

Response inline

>  > Use action instead of actionListener? Actions are always fired last.
>
>  Yes, I know. But if I use actions, PPR won't work. The whole page is
>  refreshed, regardless of the action outcome. But I'd like to use PPR.

Returning null is the correct way to ensure that the navigation
handler does not change the current view root. I have used it with
Trinidad without issues, so I know it works. If the action is non-null
it should only navigate if there is a match. Do you have any "catch"
all navigation rules (where the outcome or action are not specified)?

>  I found a solution by myself. Instead of declaring the actionListener as a
>  commandLink parameter, I'v implemented ActionListener in the backing bean
>  and used f:actionListener after tr:setActionListener. Now the execution
>  order is correct.
>
>  <tr:commandLink text="Neu" partialSubmit="true" immediate="true">
>         <tr:setActionListener from="${entity}" to="#{pageFlowScope.finding}"
>  />
>         <f:actionListener binding="#{backingBean}" />
>  </tr:commandLink>
>
>  IMHO: setActionListener should be executed before any UIComponent
>  actionListener. Shall I open a JIRA?

No, the action listeners should be invoked in the order that they are
added to a component. A setActionListener should not get preferential
treatment. If you need listeners to be invoked in a specific order,
you need to make sure they are added in that order. And even then, the
JavaDoc of UIComponent does not guarantee that the listeners will be
returned in any specific order:
http://java.sun.com/javaee/javaserverfaces/1.2/docs/api/javax/faces/component/UIComponent.html#getFacesListeners(java.lang.Class)

Maybe the spec. says something?


>
>  --
>  Kind regards,
>  Mathias
>
>
>
>  >
>  > On Tue, Apr 15, 2008 at 3:51 PM, Mathias Walter
>  > <mathias.walter@gmx.net> wrote:
>  > > Hi,
>  > >
>  > >  is it possible to use partialSubmit without an
>  > actionListener and only with
>  > >  an action on a tr:commandLink? I tried it, but the whole
>  > page is refreshed
>  > >  not only the relevant part.
>  > >
>  > >  I'd like to use actionListener, but unfortunatelly a
>  > tr:setActionListener
>  > >  will be executed after actionListener. In such case, it's
>  > impossibel to set
>  > >  a pageFlowScope variable with setActionListener.
>  > >
>  > >  Example:
>  > >
>  > >  <tr:commandLink actionListener="#{backingBean.add}" text="Neu"
>  > >  partialSubmit="true" immediate="true">
>  > >         <tr:setActionListener from="${entity}"
>  > to="#{pageFlowScope.data}" />
>  > >  </tr:commandLink>
>  > >
>  > >  This does not work, because backingBean.add is fired before the
>  > >  setActionListener.
>  > >
>  > >  --
>  > >  Kind regards,
>  > >  Mathias
>  > >
>  > >
>
>