I'm fairly certain that using <redirect /> loses f:param data and
t:saveState data because it causes two lifecycle invocations -- first
the old page is reloaded and the action is executed. Then the
navigation rules force a second lifecycle invocation to create the new
page.
That said, I've never used f:param with a commandLink to pass data to
a new page.
On 11/16/05, ::SammyRulez:: <[EMAIL PROTECTED]> wrote:
> i notice that if I have a page with a action that drive to another
> page like this
>
> <h:commandLink action="EDIT_USER" >
> <f:param name="id" value="0" />
> <h:outputText value="#{labels.new}" styleClass="text"/>
> </h:commandLink>
>
> with a navigation like this
>
> <navigation-rule>
> <from-view-id>/jsp/admin/listUsers.jsp</from-view-id>
> <navigation-case>
> <description></description>
> <from-outcome>EDIT_USER</from-outcome>
> <to-view-id>/jsp/admin/editUser.jsp</to-view-id>
> <redirect />
> </navigation-case>
> </navigation-rule>
>
> the page with the command link is reintepreted before loading the target page.
>
> I mean that the methods in the beans in the from-view-id are called
> before loading to-view-id page and calling the methods of the
> o-view-id page beans.
>
> I tried with and without redirection but with no effects...
>
> any suggestions?
>
> Thanks
>
>
> --
> ::SammyRulez::
> http://sammyprojectz.blogspot.com
>
