Dave wrote:
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.
It feels to me like you're fighting the system.
JSF is not Struts, which is "url-oriented". JSF is a *component*
framework that is more like Swing than like Struts in many ways. So
state should not be carried around as "url parameters" but instead by
setting state on the appropriate JSF components or model objects.
By "click send email", do you mean that the user is selecting something
in a JSF page? If so, the Email page should be getting the send-to-email
and subject values from some model object, so the fact that you redirect
to a login page in the middle isn't an issue.
Or do you mean that the link is somewhere on a web page that is *not*
part of the same webapp? In this case, it seems to me the problem is due
to trying to leap into a webapp from outside the webapp, ie is an issue
with integrating standard HTML with JSF not a problem with JSF itself.
In this case I would suggest having a special servlet (not a JSF
component) that looks into the request parameters, updates some MODEL
object in the session then redirects to the JSF page. When the JSF page
runs, it will then see your model has the send-to and subject set, and
will render them. Note; I've not done any of this myself, I'm just
speculating here.
Regards,
Simon
