> > i find having the relationships in the DTOs useful as it enables the > DTOs to be the *real* data model, rather than the database. for me, it > is easier to model a business problem as an object model rather than a > relational model as u get easy inheritence, etc. for us this translates > to much more agile development/maintenance process. of course u get > back to the old trade-off of convenience/speed vs performance. >
Here's where we have a design difference, I guess. I want the object model to be at the BO layer, so they have the relationships, dependent objects, etc. I'm all for using an object model, inheritance, etc. I just know that it's so frequent that I have to send a row's data someplace, I want the data in the DTO. Note that I like to use views to support inheritance in the object model, though that fits best when you don't have a lot of extra attributes in the various derived classes (otherwise the union of required columns in the base table makes it a "wide" row w/ lots of nullable columns). FWIW... Donnie _______________________________________________ Hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
