I'll take the opposite opinion from Paul, simply from the fact that if you have Stored Procedures without Hibernate, you will have lots of JDBC code that translates the return results from stored procedures into your
Java classes, which I always find error prone and harder to maintain.
That said, there is still lots of merit to Paul's post. For instance, there are lots of ways to get better performance out of Hibernate than through a stored procedure with Caching. And I find that an all SP solution is not flexible, maintainable, and leaves you vendor locked as Paul has said.
Personally, in today's technology, those people that fight for an all SP solution are out of date.
Mark