--- Gena Batsyan <[EMAIL PROTECTED]> wrote:
> This is a simple requirement, that is needed in
> almost any webapp I can imagine, and I absolutely
> believe something like this must be a core
> feature.
I'm not entirely sure I complete understand what
you're asking for.
The *most* common solution for this is a
post-redirect(-get) where the form is posted,
processed, and you redirect to the list.
Messages for that are generally stored in a
"flash"-like context (session but with automagic
removal after the next request completes).
If your list action isn't ParameterAware it won't get
any params anyway, I believe.
> (it kills the valuestack object in the request
> map as far as I have seen while debugging, which for
> some obscure reason prevents the final JSP to obtain
> any of the properties of ListAction)
Some "obscure reason?" The value stack is where the
properties of the list action are *kept*. Of course if
you remove it the properties will be gone.
If you want to forward, the "best" way to do it is
with an action-chain. If you want to redirect then you
need to have some way of storing the message, like you
said.
That's just the nature of HTTP, AFAICT. You can work
*around* the limitations of HTTP with interceptors,
parameter map tweaking, etc. but you can't *avoid*
those limitations.
Someone else might be more helpful, though.
d.
____________________________________________________________________________________Pinpoint
customers who are looking for what you sell.
http://searchmarketing.yahoo.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
