I don't know why (I've been doing struts development for years, but I guess we've always been very explicit in our struts-config files), but only recently did I discover that this was the default behavior for form beans. And I'm trying to figure out, mostly on a higher level, on a theoretical level this is this way. I'd like to understand what is it about session scope that's preferrable as a framework. Not being judgemental. Just curious if we're missing the boat by using request scope most of the time and session some of the time. I know some other frameworks like Tapestry make heavy use of the session. So I'm wondering if there's just something understood about web frameworks that putting everything into session scope is "better" and the user is meant to sort out resetting the form or if this was a choice made by the Struts team for other reasons.
Preston --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
