Hi all,

I'm relatively new to Hibernate and I want to know if the architecture describe above is good with the use of hibernate for my web project.

I'll try to explain a sample supplier sample, where you can create, update, delete and list the supplier from a supplier table via a web page. I would to apply this kind of architecture for all table of my system.


Web page (jsp) --> MVC layer (lets say Struts action) --> ServiceSupplierBean (SessionBean) --> SupplierDAO (sql call with Hibernate) --> Supplier table (database)


where --> mean "call" or "access"


Is Hibernate good for this kind of architecture and if not why ?

Thanks to all who will reply this post

This is a common approach. Go for it.