Re: mod_plsql vs java-based apps ++ mod_owa
Date: Wed, 1 Sep 2004 10:46:59 -0400
"pstnotpd" <schoenmakers_at_tpd.tno.nl> wrote in message
| > pl/sql issue, regardless of presentation layer -- although this could be
| > minimized
| As mod_plsql is the presentation layer and this only works on oracle,
| what do you mean by minimized?
for an implementation that is initially all pl/sql (mod_plsql for the UI), if the pl/sql is coded so that business logic and data qaccess are separate from presentation logic, then changing webserver and presentation layer requires rewrite of just the pl/sql UI packages, presuming the new UI can call the existing pl/sql business logic and data access code
more to the point of my reference to 'minimized' -- if the application is initially implemented with a presentation layer other than mod_plsql, but relying on calls to PL/SQL SPs in an oracle back-end, then changing the back-end requires rewriting the PL/SQL businesss logic and (some of) the data access code (presumably substantial amounts SQL would be reusable) but the UI should (as in should, not can) be able to call the non-PL/SQL SP's with hopefully little modification -- but that requires coding the original app with a suspicion that it may one day be non-oracle
so, my point was, if you you PL/SQL with any UI (mod_plsql, .net, Oracle Forms, JSP, etc.) and change out the database, you have the same issue with the business and data access logic, but may be able to salvage the UI if it is not mod_plsql.
++ mcs Received on Wed Sep 01 2004 - 16:46:59 CEST