Maybe what we need is an abstraction over the current request mapping stuff. If you think about it, what Struts basically does is mapping a request from a browser to some class that then executes a method (I know Struts has a lot more things, but this is the main one). Maybe we could go a step further, and think about wizards, page flows, data associated with those flows, and why not, set the bases for a direct translation from use cases to one of these abstractions.
Please, don't take this as criticism to Struts. I think Struts is a great framework and I'm using it and will be using it in whatever J2EE project I do, but maybe we could start thinking a level above... what do you think?
Rick Reumann wrote:
On Fri, 7 Mar 2003 10:34:13 -0500 Sundar Narasimhan <[EMAIL PROTECTED]> wrote:
Over on another mailing list I'm on the consensus is that
continuation-style programming is much better than the present
approaches suggested by struts and other frameworks. In particular,
they solve the back button/refresh type problems much more cleanly
than other languages/frameworks.
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?
