On 12/15/05, Paul Benedict <[EMAIL PROTECTED]> wrote: > > > As I said, the problem is you're using model objects for input. Don't do > that. Your "load" action > should convert the specific and limit poritions of your intended user > input into the Form; > probably a list of Strings. In your "save" action, you convert them back > into the model object.
You're missing what I'm saying. You can't easily do what you are saying with nested items. Very rarely do I ever need nested objects in Struts, in my experience. I've > done Struts for about > 3 years now and I think only one time I had to do it in a big business > application. Usually, all > the user needs to do is update a simple list; so typically you can pull > out all your nested data > into a simple array. Well, my experience has been just the opposite and have been using Struts for over three years. I'm usually dealing with business applications where things are much more complex than you describe.. and that's been the norm not the exception. Later when I get back from seeing the Lion The Witch and the Wardrobe, I'll provide even some simple cases that make much more sense to have nested objects.... Larry if you read this.. explain the deal with the Department id situation:) I got a run.. -- Rick
