Ok, please excuse me for being a big dumb turd, I haven't touched Java in 3 years.
There's this IoC craze going on and I'm trying to get with the program. I'd like to understand, what was the design justification in having DAO's generated for each entity in the domain model and (in my case) quadrupling the number of classes in my domain model? I understand that IoC is supposed to allow me to change my data access method with out having to change alot of code all over my app, but the code is all over my app, in a million DAO's. That alone doesn't stand as much of a reason to me, primarily because I would rather have the CRUD code part of controllers seeing as how these O/R mappers are getting so simplisic and mature (read calling hibernate directly). More coherently, how is: MyEntityDao myEntityDao = (MyEntityDao)factory.getBean("myEntityDao"); MyEntity myEntity = myEntityDao.create(firstName, lastName); myEntity.setSomeRelationShip(someOtherObject); myEntityDao.update(myEntity); better than: MyEntity myEntity = new MyEntity(firstName,lastName); myEntity.setSomeRelationShip(someOtherObject); hibernateSession.saveOrUpdate(myEntity); _________________________________________________________ Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=1674#1674 Posting to http://forum.andromda.org/ is preferred over posting to the mailing list! ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Andromda-user mailing list Andromda-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/andromda-user
