Subject: Re: DynaActionForm example From: Vic Cekvenich <[EMAIL PROTECTED]> === And another thing: Say I have a FormBean on One Page. But then I need its properties on another page that has other beans. If I lareay unit tested it, I can reuse. Specific example in use: I have a Properties Form that has an information about a building property. Then I have a Loan form. The loan form needs to display information about the properties. In XML dynabeans, I would have to code the XML 2 times.
Vic Cekvenich wrote: > It was not set up for a bite, I just talk a lot on my opinion, and > sometimes learn when I get feedback. > > The FormBean lets me code in Java (vs Dynabeans XML). It lets me format, > validate, convert, do complex look ups in other beans. It lets me have a > bean that contains (somtimes iterated sometimes multiple) beans. It lets > me hide the data model (at least the way I use it). So if the data model > changes, I have one place, the Bean. > I also have other uses for my Beans, not just Struts, ie. SOAP. > Say I have my BaseFrmBean that has a DAO. The DAO has a complex sql join > string (Some of my clients have a 16 way joins in DAO). Then my Form > Beans have getters and setters (that use the DAO). When I look at the > Strus applications I have writen, my getters and setters are somtimes > dozens of lines long in every FormBean. I could post good long setters > or getters examples. > Say I have a CLOB, or other. Or (manual) O/R mapping. > Or lets say I have dynamic options on a page. So I need a getOption and > getOptions. With a 1:1 bean to a page it makes it easier. > Or Multi Line updates. Dynabeans are only for simple. So sometimes I > would do XML code sometimes Java, so why not Java Beans all the time. > In a real world application, things are not straig forward, and a getter > and a setter can do anything. Dynabean would only be for simple things > or a prtotype. > Also... debuging. MultiLine updates with master detail gets a bit complex. > I can unit test the FormBeans, before ever using it in Struts! > Or errors. If the getter comes from another place. > Or row based security. > > But for the same reason I do not like the SQL tag. I like the phsyical > separation of the data model. An bean enitty does not have to be a > single table. > I realy like the clean lightweight MVC. A Bean is simple and powerfull > and great architecture for people to whatever they want. I like > practical and KISS. Skiping a layer can get confusing to new people and > does not work when it is a realistic application. > Also, most IDE's now generate the getters and setters, based on a > property list you give them (CodeGuie from Omnicor I use) so if it's > simple, it is simple. > > Vic > > > Craig R. McClanahan wrote: > >> >> On Tue, 30 Apr 2002, Struts Newsgroup wrote: >> >> >>> Date: Tue, 30 Apr 2002 07:25:01 -0700 >>> From: Struts Newsgroup <[EMAIL PROTECTED]> >>> Reply-To: Struts Users Mailing List <[EMAIL PROTECTED]> >>> To: [EMAIL PROTECTED] >>> Subject: Re: DynaActionForm example >>> >>> Subject: Re: DynaActionForm example >>> From: Vic Cekvenich <[EMAIL PROTECTED]> >>> === >>> Err... just a note: I am not sure if Dynabeans is the best parctice. >>> Regular beans isolate the application a bit better. >>> my 2 c. >>> Vic >>> >> >> >> OK Vic, I'll bite ... how is using a DynaBean for your form bean any >> different than a standard ActionForm bean? The only difference I can see >> is whether or not you have to write an extra class yourself, or let >> Struts >> configure it dynamically. >> >> Craig >> >> >> >>> James Mitchell wrote: >>> >>>> The struts-example uses it for Logon. >>>> >>>> >>>> struts-config.xml >>>> ----------------------------------- >>>> ... >>>> ... >>>> <form-bean name="logonForm" >>>> type="org.apache.struts.action.DynaActionForm"> >>>> <form-property name="username" type="java.lang.String"/> >>>> <form-property name="password" type="java.lang.String"/> >>>> </form-bean> >>>> ... >>>> ... >>>> <!-- Process a user logon --> >>>> <action path="/logon" >>>> type="org.apache.struts.webapp.example.LogonAction" >>>> name="logonForm" >>>> scope="request" >>>> input="/logon.jsp"> >>>> <exception >>>> key="expired.password" >>>> >>>> type="org.apache.struts.webapp.example.ExpiredPasswordException" >>>> path="/changePassword.jsp"/> >>>> </action> >>>> ... >>>> ... >>>> >>>> >>>> >>>> >>>> logon.jsp >>>> -------------------------------------- >>>> <html:form action="/logon" focus="username"> >>>> <table border="0" width="100%"> >>>> >>>> <tr> >>>> <th align="right"> >>>> <bean:message key="prompt.username"/> >>>> </th> >>>> <td align="left"> >>>> <html:text property="username" size="16" maxlength="16"/> >>>> </td> >>>> </tr> >>>> >>>> <tr> >>>> <th align="right"> >>>> <bean:message key="prompt.password"/> >>>> </th> >>>> <td align="left"> >>>> <html:password property="password" size="16" maxlength="16" >>>> redisplay="false"/> >>>> </td> >>>> </tr> >>>> >>>> <tr> >>>> <td align="right"> >>>> <html:submit property="submit" value="Submit"/> >>>> </td> >>>> <td align="left"> >>>> <html:reset/> >>>> </td> >>>> </tr> >>>> >>>> </table> >>>> >>>> </html:form> >>>> >>>> >>>> LogonAction.java >>>> -------------------------------------------- >>>> ... >>>> ... >>>> // Validate the request parameters specified by the user >>>> ActionErrors errors = new ActionErrors(); >>>> String username = (String) >>>> PropertyUtils.getSimpleProperty(form, "username"); >>>> String password = (String) >>>> PropertyUtils.getSimpleProperty(form, "password"); >>>> ... >>>> ... >>>> >>>> >>>> >>>> JM >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>>> -----Original Message----- >>>>> From: Parmar, Dipakkumar [mailto:[EMAIL PROTECTED]] >>>>> Sent: Monday, April 29, 2002 11:38 PM >>>>> To: Struts Users Mailing List >>>>> Subject: DynaActionForm example >>>>> >>>>> >>>>> can anyone point me the DynaActionForm example? >>>>> i could not able to find it. >>>>> >>>>> Tx in advance. >>>>> Deepak >>>>> >>>>> -- >>>>> To unsubscribe, e-mail: >>>>> <mailto:[EMAIL PROTECTED]> >>>>> For additional commands, e-mail: >>>>> <mailto:[EMAIL PROTECTED]> >>>>> >>>>> >>>> >>>> -- >>>> To unsubscribe, e-mail: >>>> <mailto:[EMAIL PROTECTED]> >>>> For additional commands, e-mail: >>>> <mailto:[EMAIL PROTECTED]> >>>> >>> >>> >>> -- >>> To unsubscribe, e-mail: >>> <mailto:[EMAIL PROTECTED]> >>> For additional commands, e-mail: >>> <mailto:[EMAIL PROTECTED]> >>> >>> >> >> >> -- >> To unsubscribe, e-mail: >> <mailto:[EMAIL PROTECTED]> >> For additional commands, e-mail: >> <mailto:[EMAIL PROTECTED]> >> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
