JSP is not being made for the purpose of writing java code in it. It is for presentation. Other than complexity, maintainence is also the major problem, I can think of...
May be someone else can put more light on this...
That's a lot of light already
It will help to understand the historical growth of server-side Java programming - the times when they introduced servlets, what motivated them to come up with JSP, and the realization of the need for a more MVCish arrangement, and so on. Someone elaborate this?
My typical request from a browser will first go to a servlet which if nothing else will check the users session is still valid and not timed out before using the requestdispatcher to call up whatever jsp is required.
I suppose I could have a filter to check the session of each request but this is just the way I've got used to working in.. So if each servlet has anything else to check its easy to put the code in without having an ever growing filter..
Regards, Dave Brown
SCJP 6 - [url]http://www.dbws.net/[/url] - Check out Grails Forum
Joined: Dec 19, 2005
in old MVC we have JSP as the controller why have they replaced it to servlet as the controller what ever we do in servlet we can do everything in JSP.may be for performance issue they will be takindg servlet as the contorller because JSP is converted into servlet..(it takes some time for this conversion)... if any one knows give more reasons why servlets are used as controllers.