it may not be feasable in your situation, but I have used the tomahawk sandbox form tag for a situation like this (taking a restful URL and using the value on a request scoped bean). it allows you to specify an action attribute, which works like a normal html form. unfortunately you also have to use tomahawk commandLink and possibly other tomahawk components.
On 1/8/07, Simon Kitching <[EMAIL PROTECTED]> wrote:
Olof Næssén wrote: > Hello! > > I have a jsp page which is reached by using a commandLink with a > parameter. In the page I have a form with validation. If validation > fails, and the user is redirected back to the page, the parameter is > lost. Is this expected behavior? Is there a way around this? Hmm..you have page A which has a commandLink that encodes a URL for page B with a parameter? Why would you use an f:param tag rather than using t:updateActionListener? Anyway, in page B, obviously no validation is going to occur on first access, because this is not a "postback" to page B; this is simply a "first render" of the page. The special parameter value *will* be accessable at this point. Are you somehow then expecting this parameter to continue to exist as page B is submitted? It won't be. Instead, just copy it into the "backing bean" for page B on the first render... Regards, Simon
