If I read this all right I would approach it by option 2: > should I create the guide object from the query, populate the form with the > getters and use the setter methods to make any changes before passing to the > DAO?
This is the better option - this also means that if you persist your BO, you can go retrieve the object from your pool, and avoid having to hit the DB. > Do I need to create a structure from the query and pass the structure > as the argumentcollection to the init function? You can do that. You can also have a 'default' (no argument) init function, and a getMemento() and setMemento() functions that retrieve and all the inner values of the BO - much like the setInstanceFromStruct() function tha Nando pointed out. The stuff Nando posted is good - however, do note, that sometimes BO's can represent more than 1 row in a database on a single table, especially if they are composite of several other BO's - and then it can become interesting as to how you want to populate your Business Objects in DAO's. (And you can also get into a discussion on how to do things if you want to pull an array of BO's from a method, howabout you go about doing that - and even if you should...) Hope that helps somewhat. Mark -- E: [EMAIL PROTECTED] W: www.compoundtheory.com ICQ: 3094740 ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com). An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
