On 1/6/06, Frank W. Zammetti <[EMAIL PROTECTED]> wrote: > The interesting thing is, there are some relatively minor tweaks that > could be done to Struts that would solve a lot of problems. How about > creating Actions per-request? Not at all a significant enhancement, but > think of all the things you could then do. How about a simple flag to > tell the RP to populate the Action rather than an ActionForm, thereby > giving Michael his dream of a combined Action and ActionForm? Again, > we're not talking about a big change. These are also not new ideas by any > stretch, I, and you, and Michael and others have been tossing these things > around for at least a year or more.
You're right in that these are not new ideas. I think crazybob implemented something like this a few years ago. I tried it out myself, and was having a lot of fun with it (yes, i'm a geek), but I don't have the time to pursue it right now. Anyway, with Ti, this should no longer be a problem. > ...all of which raises a question that I don't know the answer to... does > Struts 1.3 pool Commands? I.e., if I implement my Actions as Commands, do > I get that per-request functionality I want? If so, that is at least a > step in a good direction. IIRC, Craig implements Commands the way he did Actions, so there's one instance of it for the whole app (per jvm, etc, you know what i mean). > No one thinks Struts is perfect, but based on how many people > use it and use it successfully, it's probably not fair to say it's poor, > or that any one part of it is poor. *Poor* is relative. Struts might've been the bleeding edge of tech years ago, but it's got a lot of catching up to do now. Not that it can't, but instead of slowly catching up, we'll quickly catch up instead by merging with WW. > Frank Hubert --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
