PL/SQL reuse in ADF

Question

Is disabling the use of application module pooling good practice for intranet applications where the number of users are known in advance (although in the thousands)? This was suggested as a solution to limit the amount of recoding that will be required of existing PL/SQL programs that make extensive use of global temp tables/package variables/etc. By disabling pooling (and a few other tweaks) the user will access the db with the same session and hence database state is preserved between requests. But in my experience a lot of PLSQL code is written to fit specific use cases (mostly on Forms) without considering the need to reuse the code in any other context (although I must admit that it can easily happen in any other language). I have repeatedly tried to explain that state is better maintained and much easier to deal with if it sits on the application but perhaps I'm wrong. Any advice will be much appreciated.

Answer 1

Hi,
its not enough. If you want to build an ADF application that behaves like Forms, then you need to look for implementing dynamic JDBC credentials so that users have dedicated database connections (which is what Forms is doing). Note that using Application Module pooling and database connection pooling is guaranteeing you better performance so that the question is what the required changes are (global PLSQL variables need to be removed for sure) to PL/SQL so the logic can be used in ADF applications that follow best practices (which is that they run as true Java EE web applications)
Frank