Just use EL,JSTL, Custom tag library, AJAX, Oracle stored procedures for (DML)
Look at myspace and all those million PHP sites out there, they are not using any fancy MVC framework and yet they are thriving. MVC for webapps is an overkill because most of the frameworks out there put too much emphasis on the M and the C and not on the V, when in reality you really need to simplify the V. JSF is one framework that provides re-usability in the "V", but its M and C is tedious.
IMO, editing XML files for defining and validating fields on a JSP page and defining how to navigate from one JSP to another is so "non-intuitive". Why not keep all that is JSP related inside the JSP?.
As your project increases, the # of XML mapping, config files you will need to maintain will also increase.. whereas if you stick to JSP and smart tags
(commercial tag library, JSTL, EL), you will just need to stick to JSPs.
Now, you said you are moving to Oracle so that you can use stored procedures. Obviously you plan to do some DML in these procedures. Why do you need Hibernate at that point?. Hibernate is good if you are doing all your persistence in the Java layer. Keep your persistence code in either the database layer (stored procedures, triggers) or the Java layer. Don't spread it in different layers.
Which brings to the M and the C. You can write a single
servlet that would be your front controller and use convention over configuration (i.e., derive navigation from jsp naming
patterns). Thats what Ruby on Rails uses. The only reason you need M is for Hibernate and if you are sharing Pojos in some other project. IMO, M without
EJB is a waste. What purpose does a pojo that maps to a form on a JSP serve?. Its a throw away. Remember as you add more pages there will be more pojos to write...