Yes; this confused me too - are there now: DAO - used to read data from DB DTO - to transfer data to app BO - to store/manipulate data for a particular "thing"
and how do any/all these interrelate with each and the Forms framework...
IMHO you shouldn't let these distinctions confuse you, as they are not very relevant to the interactions between Forms and java objects.
Assuming your java object contains a field X, what Forms does (through Forms bindings that you define), is to use a getX() method to read the value of X when form.load is called, and setX() to set the value of X when form.save is called. That's it - as long as the java object implements these methods you're fine.
Forms does not care the least whether you consider the java object in question to be DAO, DTO, BO or whatever O one wants to call it. These distinctions are only relevant to the organization of the java code, which Cocoon does not force you to write in a particular way.
Of course, in a complex java app it would be good to have a clean structure using these concepts, but if you're trying to understand the relationship between Forms and java code, you should not worry about them.
-Bertrand
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
