Hunter,
my 2c worth. Leave out the EJB portion and it should be fine. It does not
add value to your objectives. EJB is for biz logic portability and reuse. Of
course it is doable but why?
Lionel
----- Original Message -----
From: "Hunter Hillegas" <[EMAIL PROTECTED]>
To: "jBoss" <[EMAIL PROTECTED]>
Sent: Wednesday, December 06, 2000 12:20 PM
Subject: [jBoss-User] J2EE Too Much for Small App?
> I am new to J2EE.
>
> I have been using Servlets and JSP for some time but have never touched
EJB.
> I recently took a class from Sun on J2EE and I want to get started with
some
> of it.
>
> I have a Web site that's currently powered by PHP and mySQL called
> RateVegas.com.
>
> I've been planning a total site makeover for several months with many new
> features. I've decided to move to PostgreSQL and Java.
>
> The question is whether to use JSP/Servlets/Taglibs or to include EJB in
> that equation.
>
> What I'm really asking is if J2EE is "too much" for a relatively simple
> application?
>
> RateVegas.com basically lets users rate hotels and restaurants in Las
Vegas.
> There is a fair amount of DB activity but they are simple queries.
>
> The new version of the site will be totally personalizable and will be
> somewhat more complex.
>
> Do you think using J2EE is overkill?
>
> Hunter
>
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
