To enable action chaining in an intuitive way, it seems that when the ActionServlet is called, it can look for an attribute in the request that indicates whether it has run before in this request. If the attribute is not there, do everthing and then set the attribute; if the attribute is there, don't reload the action form and don't reset the action errors collection and don't do anything else that intuitively should be one-time-only.
Or maybe it's the request processor that's modified, in the same spirit. I've just had the idea, haven't actually looked at the code. Of course, this is so obvious that it must have been discarded already with good reason. So, before I find out why it's not reasonable the hard way by implementing it, please tell me where the hidden problems lie. Thanks, Derek Richardson --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
