I think small systems will be profit from mvc1 since they do not need the overhead of a full scale mvc2 installation
only 20 jsp's Why indeed would I need to create the overhead of actionforms, xml config files, actions etc, (maybe tiles) if it can be done in 20 pages ?
It is the same as you will not have EJB's in your application
why then use WebSphere if Tomcat will be enough?
In addition, on the development effort, of course it might be easier for developing for single JSP to work out everything, but then it is hard to maintain and reuse if some functions should be common.
This argument seems just backing to the old days that, if I just have small applications, why I need to maintain so many OO classes? I could simply put in everything into 1 or 2 objects to make it works.
Originally posted by Nicholas Cheung:
But I wonder any systems in production really use Tomcat. Since there is lack of technical on-call support, thus, I guess only small systems from small firms will use Tomcat in production.
Which is exactly why only small applications (be it webbased or not) will benefit
Well, practically every single Java hosting provider out there is running Tomcat. That makes a lot of business
There is no such thing as MVC1 or MVC2
There IS a Model 1 and a Model 2 architecture. Model 1 is client-server. Model 2 IS MVC.
This is a very common mixup because the word Model is also what the M stands for in MVC.
That is to say, if your write small applications, even you use Java, you will use 1 single class or as small as possible classes for it?
Well, however, I have just worked with Tomcat in the testing environment, and I havent had any applications that eventally deployed on Tomcat
Really having a mix? So far, I havent developed any systems that using JSP as the controller, as if we do so, then, a single JSP might contain thousands line of codes which is very difficult to maintain and reuse the code in future.
Originally posted by Marc Peabody:
Model 1 has nothing to do with the MVC pattern.
This approach ["MVC1"] combines Controller and View functionality within a JSP page and therefore breaks the MVC paradigm.