I prefer to do lots of little apps tied togoether by the data they share in
an enterprise database (I'll admit the term enterprise database is
optimistic but I've just done two years at a client who started his IT shop
from scratch, so I'm spoiled).
The many apps to one db patttern was practical, even pre-j2ee, and I find
the the servlet/jsp/jdbc paradigm conceptually covers that pattern and
allows better implementation patterns (eg front servlet) in the middle tier.
I'm just getting into ejbs and expect to share them between web-tier apps.
Discussion on this list indicates that it can be done, using orion. Thus,
in the ideal world, I expect to develop lots of little apps using fewer ejbs
against very few enterprise databases.
Unless there are technology constraints I dont know about, I will DEFINITELY
NOT go down the path of one humongous app. That way lies maintenance
madness. Much better to learn techniques for efficiently sharing
extensions, ejbs, database, etc. in a deliberately modular way.
My 2c
Bill.
----- Original Message -----
From: "darl zero" <[EMAIL PROTECTED]>
To: "Orion-Interest" <[EMAIL PROTECTED]>
Sent: Wednesday, May 09, 2001 2:42 PM
Subject: common practice for configuring orion app/web-site
> Hi,
>
> This might be sort of a newbie question or just a very
> general one. I tried looking through archives before
> posting but no luck, maybe someone has a quick anwser.
> I would like to know if most of you break up your
> projects into a lot of small apps and bind this to a
> web-site, or do most of you just pile all the apps
> into one big one.. so that there is only one
> application running on one default-web-site.
>
> -p
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Auctions - buy the things you want at great prices
> http://auctions.yahoo.com/
>
>
