I don't see anything wrong with your setup. Keep in mind that the reason you have 2 hierarchies is so your business layer doesn't know what environment it's running in. You can reuse your model beans in a swing application with no changes. The form beans are only used in a struts web environment.
You could pass your form beans directly into your business layer but that's not very elegant and will be frowned upon by most architects. David >From: "Dan Tran" <[EMAIL PROTECTED]> >Reply-To: "Struts Users Mailing List" <[EMAIL PROTECTED]> >To: "Struts Users Mailing List" <[EMAIL PROTECTED]> >Subject: FormBean Vs ModelBean dilemma >Date: Wed, 16 Oct 2002 10:20:37 -0700 > >Hello, > >I am seeking for some advice on the best way to implement my project > >I have a bout 20 screens to display and persist into DB. >I follow the tutorial on > > >http://www.keyboardmonkey.com/pilotlight/next/Tutorial_partTwo.jsp?content=y >esplease > >and implemented my prototype and ended up with 2 similar java object >hierachies. One for the >form bean and one for the model bean. As recommend by all expert on this >list as well as Chuch's book, >All action form bean's properties are String, the actionform beans are copy >to the model beans to be persisted. > >The dilemma here is I have 2 similar groups of objects (and lots of set and >get methods to type) and scare the hell out >my boss ;-) > >Any suggestion? > >-Dan > >-- >To unsubscribe, e-mail: ><mailto:[EMAIL PROTECTED]> >For additional commands, e-mail: ><mailto:[EMAIL PROTECTED]> _________________________________________________________________ Unlimited Internet access -- and 2 months free! Try MSN. http://resourcecenter.msn.com/access/plans/2monthsfree.asp -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
