1) I use session-scoped ActionForms with "extra" fields plenty (in search scenarios for example, where the form is for search, where the search is related to a product, and where you want to hang on to the product details as the search results change) and couldn't care less who "frowns upon it". Why do you care?
2) Implementing a session "cleanup manager" is much easier if you *do* associate keys with paths (path == scenario/set of related use cases) and if you nest the attributes in Maps. Remove the base Map, remove everything. Remove a scenario-level Map, remove all attributes associated with that scenario. Remove a higher-level Map, remove attributes associated only with one use case or view. I use a request processor extension, where I'm already tracking user navigation. Cleaning up the session is a related operation. I usually don't bother to clean up at the page/use case level, but rather at the scenario level. When a user is done with that scenario, I remove that scenario's Map. This is of course, implemented by removing everything that doesn't pertain to the current scenario (usually triggered by a return to a home/base page). Erik --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
