>> I'm concerned with having to deal with that limitation then how DO you deal >> with the 'model/domain/business' objects that do need to get populated? Sure in a simple form it's easy, but real life is a different story. Many times you get back objects that are nested in Collections...
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. 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. Paul __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
