I agree it could be made easier. I'd like to see it combined with a flash scope-type interceptor so that more than just messages could be passed via the session automatically.
As for your solution, you could implement the SessionAware interface and get the session map directly, then you could do whatever you want. Don On 9/21/07, Adam Hardy <[EMAIL PROTECTED]> wrote: > From the javadocs, this interceptor seems to have a relatively complicated > configuration that caters for situations over and above what I need relating > to > message and error caching when redirects are involved. > > A solution to simplify MessageStoreInterceptor would be where it puts the msgs > and errors into the session on one call and automatically switches its state > from STORE to RETRIEVE. On the next request after doing whatever RETRIEVE > does, > it could then automatically flip to STORE state. > > Would that work? > > Another solution would be if the messages and errors are stored in the session > all the time and then removed once they have been displayed, e.g. by the > actual > actionmessages or actionerrors tag. > > Can I abandon the MessageStoreInterceptor then and somehow tell S2 to put the > actionerrors straight into the session? Then I could extend the taglib to > remove > them when displaying them. > > > Regards > Adam > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
