For my $0.02 worth I think using the form-bean in the database layer of your application is a bad idea any time. By doing so you are directly tying your presentation layer to your database layer. Any changes to one now have to be measured against the other. Granted most changes to your application are going to impact all layers of the design, but you lose the flexibility of exposing your database layer to other applications when it is directly tied to a specific presentation.
HTH, Mark N. >From: Mike Duffy <[EMAIL PROTECTED]> >Reply-To: "Struts Users Mailing List" <[EMAIL PROTECTED]> >To: [EMAIL PROTECTED] >Subject: When is it bad form to use form beans? >Date: Mon, 15 Apr 2002 20:29:17 -0700 (PDT) > >When is it bad form to use form beans? > >For example, if you are processing a web page with several form >fields and the only goal of the process is to get the information >from the form fields into the data base, is it ok to send a form bean >from the Action servlet directly to a class in the data access layer? > >You could simply do "formBean.getFoo()" into a prepared statement. > >__________________________________________________ >Do You Yahoo!? >Yahoo! Tax Center - online filing with TurboTax >http://taxes.yahoo.com/ > >-- >To unsubscribe, e-mail: ><mailto:[EMAIL PROTECTED]> >For additional commands, e-mail: ><mailto:[EMAIL PROTECTED]> > _________________________________________________________________ MSN Photos is the easiest way to share and print your photos: http://photos.msn.com/support/worldwide.aspx -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
