The parameters are dynamic and determined at runtime.  It would be nice if the navigationHandler take parameters specified in the action result somehow like:
             actionResult?p1=arg1&p2=arg2....
Then the parameters will be included in the redirect URL.
 
It is very useful. One use case:
 
When an authenticated user click "Send Email" link, but "Send Email" is a protected page. <redirect/> is required to go through login  process. Here I hope the redirect URL to carry the receiver name, and subject. When "send email" page comes up, it will have been filled with receiver and subject.
 


Mike Kienenberger <[EMAIL PROTECTED]> wrote:
I think once you specify the navigation rule, you actually
cause two requests to execute. The first one is a normal http post
that evaluates your command. The next one is a real redirect and
there aren't any request parameters preserved across that redirect, so
you can't use t:saveState or f:param to preserve the values. I
suspect the only option open is to store the data in your Session
temporarily, or to specify a non-JSF URL for the redirect and append
parameters on it ...?p1=arg1&p2=arg2....

This is my understanding based on other people's comments -- I haven't
really worked with it myself.

On 10/30/05, Nikita Koselev <[EMAIL PROTECTED]>wrote:
> I'd the same problem lately. It seems that parameter tag
> doesn't help in this situation... I mean I use tag in wrong
> way.
>
> Nikita
>
> On 30/10/05, Dave <[EMAIL PROTECTED]>wrote:
> > When a user click a command link to a protected page, a is needed
> > for navigation. I need to specify some parameters for the page. Is there a
> > way?
> >
> > Thanks, Dave
> >
> > ________________________________
> > Yahoo! FareChase - Search multiple travel sites in one click.
> >
> >
>


Yahoo! FareChase - Search multiple travel sites in one click.

Reply via email to