Lukasz Lenart wrote:
Hi,
I think the best solution is to develop two Interceptors, one will run
after action invocation and will store messages in session or some
other objects from given request key. And second one, which will be
run before action invocation, that will retrieve such stored messages
from session and put them in to the request.
Umm, that's what the Store Interceptor is.
We have some similar solution but for Struts1. We subclassed
DispatchAction and after invocking execute() method we storing in
session messaged from given request key. And before next execute(), we
are checking such key in session and retrieving them back to the
request.
I thought Struts1 handled that automatically, but ok, if what you have
works...
L.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
