Ling Wang wrote: > We are dealing with the mapping of > objects in memory to rows in database tables. The > objects are mostly not the same as OOP business > objects. They are called Transfer Objects (TO) or > Value Objects (VO).
I've also seen them identified as Data Transfer Objects. Given that DTOs are exclusively data carriers and have no behaviour, I can *appreciate* the argument that they shouldn't need to carry the overhead of the property setter/getter methods. I don't agree with it, however. I've never had Visual Studio.NET complain about the size of my source files - most are under 30KB in size, only a few over 80KB. How big are the files that you have that are causing grief? For what it's worth, the (moderate sized) applications that I've been developing with IBatis.NET have, to this point, not required DTOs at all. Instead, the mapping is direct to the public properties of the relevant domain object, avoiding a whole bunch of plumbing that would otherwise be required to create and marshall DTOs. We've avoided the pitfalls of this approach by keeping the domain objects themselves relatively lightweight, with helper (non-persistent) classes carrying specific loads. Keep Smiling, Bevan. ****************************************************************************** "This message (and any files transmitted with it) are confidential and may be legally privileged. If you are not the intended recipient please notify the sender immediately and delete this message from your system. This message does not necessarily reflect the views of the Reserve Bank of New Zealand. If the recipient has any concerns about the content of this message they should seek alternative confirmation from the Reserve Bank of New Zealand." ******************************************************************************
