Re: Architecture for web based applications
Date: Mon, 19 Nov 2001 19:49:54 +0300
Message-ID: <9tbd1e$2jt$1_at_babylon.agtel.net>
Prathap,
if you are still evaluating tools for this project, I would like to recommend you taking a look at our Dynamic PSP product. Below are your questions answered as if you were using DPSP for your project:
(1) PSP (PL/SQL Server Pages) - that is, [D]HTML with PL/SQL code insets
for database-generated content or other DML, like inserts, updates and deletes. (2) DPSP objects and/or PL/SQL packages will allow you to reuse your code effectively. (3) JDBC is not required - PL/SQL is native to the database and works a lot faster when it comes to DML. For data visibility constraints you can use dynamic query rewrites and/or virtual database - these features are supported by 9i database. (4) You can isolate business logic at either PL/SQL packages level or at DPSP objects level. (5) You can set default values and/or not null checks on your table and insert all columns always - database will throw an exception if any column violates constraints set on the table - you can catch such exception in PL/SQL and act accordingly. As of unknown or varying number of form parameters - Dynamic PSP allows any object to accept any number of parameters whose names, values and existence on the form are unknown at the time of object creation (you can call this feature 'late binding' of parameters). -- Vladimir Zakharychev (bob_at_dpsp-yes.com) http://www.dpsp-yes.comDynamic PSP(tm) - the first true RAD toolkit for Oracle-based internet applications. All opinions are mine and do not necessarily go in line with those of my employer.
"Prathap" <prathapk_at_hotmail.com> wrote in message
news:a99bf640.0111152348.1afe6935_at_posting.google.com...
> Hello,
>
> We are starting a new web based project. We will be using oracle 9i as
> database, oracle 9iAS for application server and Java based code as
> front end. We also plan to use JDeveloper for front end development.
>
> We are struggling to visualize end to end application architecture.
> Most of the team has worked on client/server applications.
>
> I request information/answers for the following:
>
> (1)In what language I should paint my front end (presentation layer)
> screen (Is it JSP/HTML/Servlet/others)
>
> (2)How should I separate business logic from presentation layer? What
> language I should write? Will I be using EJB for reusable components?
>
> (3) Will I be using JDBC drivers, if I use 9iAS? Depending on the
> userid, visibility of data should be imposed.
>
> (4) We would like to maximize the reusability of components. Hence we
> thought all db-table related DMLs, we will put in database via pl/sql
> procedures. Is this approach correct? In this case, I will be calling
> pl/sql procedures from my application logic area.
>
> (5) If I put all DMLs in database, there would be lot of
> insert/update/select statements for one table depending on the user
> input. Example, if user is inserting a record, he will definetely pass
> all NOT NULL values, but he may give only few NULL values. So my
> insert statement in database should cater to all combinations. How can
> I achieve this?
>
> (6) Are there any readymade projects available on the net for this
> kind of combination? Can I refer the source code?
>
> (7) Are there any documentation/books cover these topics. I find
> individual books on database, 9iAS, JSP. But couldn't find a book
> which will explore the capabilities of the 3.
>
> Anticipating a quick reply.
>
> Prahtap.
Received on Mon Nov 19 2001 - 17:49:54 CET