> 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]>
