When I'm not coding.. I do THIS
Originally posted by Vinod K Singh:
Utility classes should not extend HttpServlet, they should be simple class only focusing on business logic. Java beans are usually simple POJO having variables and their setter/getter without any business logic.
Originally posted by Vinod K Singh:
Also instantiating servlets like-
Is not a good practice. Instances of Servlets are not supposed to be created by developer, they are supposed to be managed by container.
When I'm not coding.. I do THIS
SCJP, SCWCD.
|Asking Good Questions|
Originally posted by Ashimashi Kabashi:
When you are using Servlets for your Beans. it allows the "Tier Leakage" anti pattern to manifest itself into your application.
When I'm not coding.. I do THIS
Originally posted by Alan Yap:
Referring to the link below, I found out servlets is not compulsory in a web app. Many things can be achieved by JSP + beans alone (see the Model 1 architecture diagram inside) , at the moment.
http://java.sun.com/developer/technicalArticles/javaserverpages/servlets_jsp/
[ October 14, 2008: Message edited by: Alan Yap ]
Steve
Referring to the link below, I found out servlets is not compulsory in a web app. Many things can be achieved by JSP + beans alone (see the Model 1 architecture diagram inside) , at the moment.