Right, it is not "standard" Struts in terms of approach used. But it still is standard Struts because the library is just an add-on for Struts. It does not substitute any of Struts classes, it does not require you to use custom RequestProcessor, you don't have to use extended syntax in struts-config.xml file. The new version (1.24, soon to be released) does not even require you to extend a particular dispatching action class. You just drop a JAR file into your lib directory and use it.
There are many other libraries that add value to "standard" Struts. This is what is great about open source, don't you think so? Michael. On 11/16/05, Asad Habib <[EMAIL PROTECTED]> wrote: > Hello Michael. Thanks for your input. Doesn't this approach defeat the > purpose of using Struts though? Simplicity is achieved but then the web > app can no longer be considered a standard Struts app, can it? > > - Asad > > On Wed, 16 Nov 2005, Michael Jouravlev wrote: > > > On 11/16/05, Asad Habib <[EMAIL PROTECTED]> wrote: > >> Hello. I am new to Struts and would like some advice. Is it better to use > >> one form bean to capture data from several forms that are being submitted > >> in succession or to use one form bean per form (i.e. multiple form beans)? > >> What are the advantages or disadvantages of either approach? Also, I would > >> appreciate if you would forward me to documents on the web, book chapters, > >> etc., that discuss this in detail. Thank you. > > > > I prefer using one formbean. And one action too. Is this looks similar > > to what you want to achieve: > > http://www.superinterface.com/wizard/signupWizard.do > > > > You can read about my approach here: > > http://struts.sourceforge.net/strutsdialogs/wizardaction.html > > > > Michael. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
