Whats the pros and cons of using mappingResources vs annotatedClasses with Spring and Hibernate?

I am working on a Spring MVC project and I always used annotatedClasses... Java Classes that had the @Table, @Column etc tags within the code. I just seen a sample does use hbm.xml files to do the mapping. Which way is bettering?

Lets take it one by one.
First annotation classes :
1) It is simple and easy to maintain and learn also
2) If you have to shift to a new database then not much changes are needed.
3) If you changes some bean name in the class, less changes.
4) It also give you a view of EJB.

Second mapping XML :
1) you can gave all the mapping in one place.
2) Easier to maintain as a whole.
3) error at one place may lead to some error at another place.So some times really messy to get the error.

Third option is you can also use a mixture of both of them

Thanks,
Ajit Singh
ajits@mindfiresolutions.com
www.mindfiresolutions.com

Thanks. anyway to make "Hibernate reverse engineering" to make the code annotatedClasses style and not mappingResources style?

Sorry. Didn't get you. Can you explain briefly ?