Because you can do pretty much anything with GenericDaoHibernate that you could with UniversalDaoHibernate. Also, it seemed to cause confusion for users that there were two classes that did the same thing.
Of course, you're free to grab the UniversalDaoHibernate class from before we deleted it and implement it in your project. http://source.appfuse.org/browse/appfuse/trunk/data/hibernate/src/main/java/org/appfuse/dao/hibernate/UniversalDaoHibernate.java#r3175 On Aug 31, 2010, at 8:34 PM, sunny wrote: > > I found these line in appfuse 2.0.2 document: > • GenericDaoHibernate: A generics-based class that requires you to create a > Spring bean definition. > • UniversalDaoHibernate: A class that requires you to cast to the specific > object type. > > Why 'UniversalDaoHibernate' is disappered now? > -- > View this message in context: > http://appfuse.547863.n4.nabble.com/Why-UniversalDaoHibernate-is-disappered-tp2402539p2402539.html > Sent from the AppFuse - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@appfuse.dev.java.net > For additional commands, e-mail: users-h...@appfuse.dev.java.net > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@appfuse.dev.java.net For additional commands, e-mail: users-h...@appfuse.dev.java.net
