Really, there is no way to learn better than doing. I'd say if you've got
the hosting issues covered then go for it!
-----Original Message-----
From: Kenworthy, Edward [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, December 06, 2000 8:37 AM
To: 'jBoss'
Subject: RE: [jBoss-User] J2EE Too Much for Small App? Rocky Honeymoon!
Gosh! Lay off the guy. You have no idea why he's decided to re-write his
site, so why is everyone coming down on him like he's some kind of a moron ?
-----Original Message-----
From: fred [mailto:[EMAIL PROTECTED]]
Sent: 06 December 2000 22:20
To: jBoss
Subject: Re: [jBoss-User] J2EE Too Much for Small App? Rocky Honeymoon!
Hi Hunter,
I think you need to read this article, by Brett Mclaughlin, "Enterprise
Applications in Java and J2EE: A Rocky Honeymoon."
visit: http://java.oreilly.com/news/j2ee_0700.html
An excerpt:
All too often, people
go overboard with their applications. In geek talk, this is
called "buzzmania." Buzzmania is the tendency to buy
more, get more, and use more, simply because more
"buzzwords" are in a product. This is a large part of the
J2EE problem. With the J2EE product descriptions and
specifications reading like a meeting of exotic 12-step
programs--JSP, XML, JMS, EJB, CMP, BMP, OR, JDBC--it's
no wonder managers' eyes light up at sales presentations.
However, the reality is few companies, and few
industries, need all these services. I'd estimate 50% to
70% of the companies that have purchased or are
purchasing J2EE solutions could easily get by with a
simple servlet and a JDBC-based solution. Presentation
logic housed in the servlet coupled with database access
through JDBC would suffice for most types of
applications, including many e-commerce solutions.
Adding JSP, or another presentation technology, such as
Enhydra XMLC, makes this an even more robust option.
Regards
Fred
Hunter Hillegas wrote:
> 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]
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
