java - AppFuse Generic/Universal DAO and Manager usage -

I've been using AppFuse to build my projects for a while. And I already know that there are two approaches to the development of your DAO and manager groups:

1. GenericDao / Generic Manager approach
2. Universaldoo / Universal Manager approach

I often find that it is more convenient to use the Universal View, because I need only one class to manage all the institutions. I was always thinking that if design-wise it would be a very bad option.

What is the reason that I should like the generic version? And generally, would it be appropriate to include both classes in my application? I personally write UniversalDao / Universal Manager for some reasons:

The "normal" approach usually involves a lot of configuration : You have to configure the DAO and manager for each unit. For a medium-large model this is simply unacceptable;

You still have to cast a lot with the "normal" approach For example, with hibernation, you will be very disappointed, for example, list From & lt; Object> list and lieutenant; MyDomainClass>

With Universal, you can create a more flexible DAO which manages many (not just one) model class, for example order order, Manages items and categories.

And of course, never do two views! It can be done easily, but in any project uniformity is a great quality ;)