@JosAH
Maybe my answer was a little bit misleading. With "JSP pages can be run in any browser" I wanted to simplify the fact that the output prodced by them is (usually, but not necessarily) HTML which can be displayed in common browsers like Firefox, Internet Explorer etc. You don't need to install anything (proprietary from oracle) on the client side to view them.
But Oracle Forms cannot be viewed with these browsers by the client. To view them, you need to install a special proprietary program from Oracle on each client which acts like a browser, and this browser can only show you Oracle Forms, nothing else.
@JosAH
More precise, you should use them in a Model-View-Controller (MVC) way: don't mix database calls (model) with HTML (view) inside one JSP page. There are other framework that enforce that more: Velocity or Freemarker. Define your database calls in Java classes and use JSPs only to fomat the result for HTML output.
That's exactly the big advantage of JSP pages: you can work with any backend, not only Oracle database. By using an abstraction layer such as Hibernate, you can make sure your application will provide highest flexibility and easy changes in the future. But with Oracle Forms you cannot separate in a MVC way: you always have the database calls (model) and Form-layout (view) mixed, which makes it difficult and time consuming to change them later on.
On the other side, if you are 100% sure that you will always use Oracle in the future and no other database beside it, then Oracle forms have the advantage that you can develop them quicker by drag & drop within an easy GUI, and you don't need to pay for a programmer.