Yes,
Again I agree, it can get sloppy. So what would you
reccommend? Many servlets? many beans? Just curious
thats all. Lots of times I think there isn't much to
separate. I am asking because I strive to become a
better programmer as we all do. Advancing to higher
levels means understanding
My approach is to have some servlets and lots of beans :-)
Roughly speaking, I execute any database query in servlets, fetch data
into beans use standard taglibs to show data (mainly tags to iterate
bean collections and to get bean values). I use the request taglib a lot
too.
On Mon,
Think of it, you get sloppy, another gets sloppy, so if all would get
sloppy and just drop code wherever it came's first in mind, who will
stay and maintain the code?
I write because, I stand now bitchin' that someone else wrote whatever
his mind shit out...
Keep in mind that you develop an
.
-Original Message-
From: Felipe Schnack [mailto:felipes;ritterdosreis.br]
Sent: Monday, October 28, 2002 8:49 AM
To: Tomcat Users List
Subject: Re: JSP's, scriplets, and logic
My approach is to have some servlets and lots of beans :-)
Roughly speaking, I execute any database
On Mon, 28 Oct 2002, Matt Fury wrote:
Date: Mon, 28 Oct 2002 06:41:10 -0800 (PST)
From: Matt Fury [EMAIL PROTECTED]
Reply-To: Tomcat Users List [EMAIL PROTECTED],
[EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Subject: Re: JSP's, scriplets, and logic
Yes,
Again I agree
