Hi, In our company we are thinking of extending the RequestProcessor and overriding processActionCreate(), in order to optionally (based on a custom ActionMapping property) store Actions on the session rather than sharing Action instances across sessions. This is to minimize impact to our existing applications, as we are replacing our legacy MVC framework with Struts.
I suppose that the Struts design reason for keeping Actions stateless was that (a) this is more lightweight and (b) state is normally tracked in the ActionForm beans. Is this correct? (Unfortunately, our legacy apps do not use form beans yet). Any thoughts, comments? Thanks Dirk Heydtmann -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
