Thanks for your answer!
A quick move to the Spring framework won't be an option because we're unfortunately running a (very) old version of
Struts as our web framework.
Anyway, it's good to hear that Spring would be an alternative for future developments which can handle those typical issues. Of course the ideas and features of the whole Spring framework sound very nice.
One more question, do you know how the management of conversational state in Spring works compared to
JBoss Seam? I don't have very much practical experience with Seam but its implementation mostly based on simple Annotation looks very easy to use. Is this the case for Spring Web Flow, too?
Marco