Sorry about the format, using my phone to send this... Question below (hopefully)
---------- Forwarded message ---------- From: Miika Mäkinen <[EMAIL PROTECTED]> Date: Sat, 9 Jun 2007 14:43:39 +0700 Subject: DTO DAO Design To: [EMAIL PROTECTED] Hi all. I haven't written to this list before, i hope i am in right place. I am quite new to distributed enterprise app architecture and i am hitting a wall here. How do you usually do your dto objects so that you both can allow creation on client side and ensure client does not change properties like primary key id? I would like to keep the dto decoupled from data access, so csla type design is not what i like. This also leaves out internal constructors. Is there anything else but accessing private fields with reflection? This is not favored either as i am wishing to use ibatis as or mapper and i don't think reflection is even possible with it. Am i missing some perfect pattern? I am just so confused why functionality required by practically any app needs to be so cumbersome to achieve! =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
