Rob Hills wrote: > That said, I believe I've previously got into problems with this kind of > issue by focusing too much on the model level.
I hear you. I'm not uncomfortable with object databases, but I suspect that this whole concept of Object-relational mapping is encouraging me to think too much in a relational model. > Not sure which archetype > you are using, but in the Basic Struts archetype I'm familiar with, Yes. > I'd > be looking to empower a Manager class with the wherewithall to do the > job. I'd create a Manager class for your unnamed third object (UTO) and > give it access to the DAO(s) it needs to load/create/persist the UTOs > and return them to your Action. That's what I was suspecting I must need to do, but I'm still having trouble figuring out how I give a manager access to other DAOs. The Manager constructor gets a DAO for it's own object, but how does it access any other object's DAO? otoh, at the DAO level it appears I can make hibernate play with any objects at all... -- derek --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
