Quote:
wouldn t it be much easier to work on a table view?
Hibernate is certainly capable of doing so, although if you plan to update your entities (specifically, CREATE UPDATE or DELETE), the view must support this (which depends on your database's capabilities). The documentation states that views (as expected) are transparent to hibernate at the database level, and appear to be tables.
If you have the option of creating a VIEW for your entity, then that may certainly be the option you'll wish to choose. It's really a matter of taste. However, if you don't have the option of creating a VIEW (for whatever reasons), Hibernate can still support your requirements through a join mapping.