Hi,
Yuck, looks like an Outlook template (no offense, just a personal bias).
Anyway, a bean is really only a glorified Java object, in that it follows
certain conventions about Setters and Getters etc. But yip, it does have the
capabilities of a servlet if it extends javax.servlet.http.HttpServlet and is
multi-threaded unless you specify the SingleThreadedModel.
IMHO, I think its a good idea to seperate as much of the Java code into
bean objects as this keeps the presentation nice and clean in the JSP file.
Then, as you say, let the bean's output be placed into the generated
HTML.
--
Joe Shevland
Principal Consultant
Turnaround
Solutions Pty. Ltd.
Ph: +61-03-6224-9146 * Fax:
+61-03-6223-2556
--
Make money and the whole world will conspire to call
you a gentleman. - Mark Twain
-----Original Message-----
From: A mailing list about Java Server Pages specification and reference [mailto:[EMAIL PROTECTED]]On Behalf Of Mark Minnoye
Sent: Tuesday, March 02, 1999 3:21 AM
To: [EMAIL PROTECTED]
Subject: ServletBeansWhen you make a bean which extends javax.httpServlet , does this bean then has the same capebilitys as a servlet? I mean: has it the same multiThreated system? (created once, multiple threads afterwards)Is it a good idea to let my beans do a lot of work en then use a JSP-page to make the view using the output of the beans ?Regards,Mark
ATT00007.gif