I was thinking exactly about that... usually you could identify that bunch of actions as steps inside an use case of the system. The data collected inside that use case usually is useless outside that use case and is usually used to make a call to business logic sitting in EJBs, or business objects with JDO or whatever. (Wow, what a useful word, use). There could be some automated way to keep the data as far as you were inside those actions, and once the use case is finished, or the user aborts this use case and initiates another, the data could be deleted. For this to happen, beans should be associated to these "use cases", "groups", whatever you call it, instead of being associated to an action.
Jose
julian green wrote:
It would be neat if you could group a bunch of action definitions together and have the form bean persist while the group remianed active.
Julian
David Graham wrote:
The token approach is an easy solution. One of the sites listed was a Smalltalk web framework. It's good to look at things in different ways but you could probably count the number of Smalltalk web applications on one hand :-).Explain how some other approach handles it in any better way? Use of token to prevent duplicate submissions works for me. And what do you mean by a continuation-style programming?
David
_________________________________________________________________
Help STOP SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=features/junkmail
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
