Yeah, that's what I prefer too, but I didn't know if having a shitload of JSP's and action mappings meant that I was doing something wrong. Thanks for the input and the reassurance that I'm not doing something stupid.
~ Keith http://www.buffalo.edu/~kkamholz -----Original Message----- From: Mark Nichols [mailto:[EMAIL PROTECTED]] Sent: Thursday, July 18, 2002 12:00 PM To: Struts Users Mailing List Subject: RE: Good/Bad Practices I prefer the more granular approach, with many actions and JSPs over a more complex and generalized approach. In my case I find that having single-function actions and JSPs leads to easier coding today (and therefore easier maintenance tomorrow). I can also split the work up over more developers, rather than "single threading" development through one complex action. Our intranet application has about 60 separate 'screens', each with its own action. Maybe overkill, but for a first attempt at Struts this pattern has made life easier by far. </mark> > -----Original Message----- > From: Kamholz, Keith (corp-staff) USX [mailto:[EMAIL PROTECTED]] > Sent: Thursday, July 18, 2002 9:32 AM > To: Struts (E-mail) > Subject: Good/Bad Practices > > > > Hey everyone, > > > > I've been trying to get in the habit of using good struts programming > > practices, (without making things too hard on myself). I have another > > question for anyone that could give me some input on it. > > > > I'm working on a data entry application, and the user can make three > > different types of entries. Let's call them A, B, and C. They > each have > > some form fields in common with each other, but each has a couple unique > > fields. To add an entry, I have a separate JSP for each, and different > > action mappings for each (that all refer back to the same action class). > > This works fine. > > > > Now I'm working on an edit function for the entries. I have a > link within > > a <logic:iterate> tag that displays a link to an edit form. I > tried using > > one action and one JSP for the edits, but it gets very messy trying to > > allow for the different types of entries. > > > > Is it a bad idea to use lots of different action mappings and different > > JSP's for each operation for each type of entry, even though they are > > similar and all have to perform very similar operations? Or should I go > > to great lengths to make very complex generalized actions and JSP's that > > can handle any type of entry? I'm not sure how understandable > my question > > is, or if it's a stupid question, but I want to get this figured out > > before I spend too much more time on the 'edit' functionality. > I'm having > > some issues, and I keep redesigning the operation, so I'ld > appreciate some > > input before I rewrite this shiznat too many more times. Thanks a lot > > everyone! > > > > > > ~ Keith > > http://www.buffalo.edu/~kkamholz > > > > -- > 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]>
