Digging deeper into the struts2 architecture I can see now how the ActionErrors
tag is quite a lightweight thing.
I'd rather avoid setting up my own mechanism for handling session usage in an
action superclass as I did with struts1 - I prefer the idea of an interceptor
handling it, but as I im
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
2 matches
Mail list logo
