hows my application architecture?

[Francisco Hernandez]

I need some input on how im building my application, currently I've got a bunch of *Manager classes like UserManager, EventManager, etc with such methods like UserManager.save(User) UserManager.delete(User), UserManager.userNameExists(userName), etc and similar patterns also used with my other *Managers, and in these Managers im using my datastore directly, Hibernate in my case.
then in my web-side of things i've got Action classes that perform validation of input and if everythings ok, I call upon those Manager classes to do operations, but now I was reading about the Data Access Object, that seems to fit somewhere in between the Managers and the Datastore, what do you guys think , should I introduce another layer of abstraction?

right now its like so:
HTTPRequest -> Action -> UserManager -> Hibernate
with the DAO it would be:
HTTPRequest -> Action -> UserManager -> DAO -> Hibernate

[Kripal Singh]

Isn't hibernate a OR persistence and DAO layer . why do you want to add another one?