OK, so it looks like #2 is preferred. Should we have:
* a new Class-collections.properties file * add a new "section" to Class-conversion.properties Thoughts? Pat -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mark Woon Sent: Thursday, January 08, 2004 4:48 PM To: [EMAIL PROTECTED] Subject: Re: [OS-webwork] how to populate a list of objects from a form Patrick Lightbody wrote: Yes, but usually these types of grid input forms have N number of rows, so pre-populating won't work. I'd like to take a quick vote on the two choices: 1) The domain model has a public static Class that corresponds to each Collection, and so if we don't know what type of object to create, we look for FOOS_TYPE or something like that. The upside of this is that it is super easy to do and isn't very surprising. The downside is that if you don't have control of the objects (ie: codegen) then you're screwed. 2) Either in foo-conversion.properties or in another file (foo-types.properties) there is a key-value pair of property->Class. The upside is that this works for any object, even ones you don't control. The downside is even more optional configuration. Opinions? I think I'd prefer #2. -Mark ------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
