Hi,
> 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.
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?
--
Kind regards,
Mathias
>
> On Tue, Apr 15, 2008 at 3:51 PM, Mathias Walter
> <[EMAIL PROTECTED]> 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
> >
> >
