Seems to me there is a need for a further scope. application session subsequent_request request
Like session but attributes are removed when the response has been committed in the request following the one they are added in. Has anyone come up with a neat way of implementing this? Suppose you could have an Object that tracks number of requests it has seen. By iterating through the session objects for a certain type (marker interface?) in the ActionServlet, and removing them as neccessary. Or is there a simpler way? -- Mike W --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
