Yes, you have complete control over everything that happens in a request. The chain can even be modified at runtime to adjust as necessary. Struts-provided commands could replaced and/or new commands could be added to perform some specific purpose. I even envision new "sub-frameworks" that write a bunch of new commands, then ship them as a new project "based on Apache Struts". The best part for developers is commands are very easy to write, and can be easily unit tested.
Don On Wed, 15 Sep 2004 17:38:01 -0400, Sean Schofield <[EMAIL PROTECTED]> wrote: > > > Exactly. It really changes the way you design your application, and I > > think in a great way. It would be great to get more people using it > > to help flush out any remaining problems with it. > > > That's kind of what I gathered. This could potentially be a really big > change in the way Struts applications are written. I have a few more > questions on how this will all work if you don't mind. > > It seems like Struts will be wrapping the request info, etc. in the > ServletWebContext during the standard-request chain. And some point one > of the commands must then unpack the ActionMapping, etc. from the > Context and pass it along to the appropriate Action (I don't have the > source in front of me but this is what I would expect.) > > This raises some interesting new possibilities. You could include your > own chains in the plugins config file and use them behind your facade or > you could write your own composable request processor and use it instead > of the default one. > > > > > --------------------------------------------------------------------- > 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]
