JSP overkill ?
Posted by John_Moylan (jfp), 10 June 2003Hello all.
Well this is a discussion forum, not just for questions and answers!
I have been coding Java/JSP pages for a short while now and I'm coming to the conclusion that for the *vast* majority of sites JSP is complete overkill and the development time is considerably longer.
Mod_Perl with a templating egine or PHP (or even...gasp ASP) seems more suited IMHO
Posted by admin (Graham Ellis), 10 June 2003You're probably right. Java is a great language for larger applications / re-usable code requirements / certain graphics applications / threaded programming etc ... but it is NOT the ideal answer for everything. Certainly, on the work I do on my own web site and also on certain sites that we work with under contract, I find PHP and / or Perl more suitable - but we do have a number of training customers who are building larger / integratred systems where Java is perhaps the best long term solution.
Note that Java is marketed / pushed commercially by Sun, but Perl / PHP don't have that form of muscle behind them, being largely encouraged along by the technical community. It follows that Java is fare more likely to bully its way into applications that it's not really ideal for than the other languages that we're talking about are.
But - don't get me wrong. Java does have its place ...
Posted by Custard (Custard), 11 October 2003My 2p'th!
I've been working on a J2ee project since June that doesn't just use JSP & Servlets, but adds extra complexity by using Jakarta Struts.
It's taken ages and ages to get to a point where I'm only halfway through the webapp part of the project. I actually prototyped many of the pages with a perl webapp of mine within a week. For this project, I believe it would have been more appropriate to code the webapp in perl, and the data handling in Java. The project has few users who would only typically use it a couple of times a day.
In fact in a Jakarta Struts app you are encouraged to put as little Java code embedded in the JSP as possible and use the Struts tag libraries.
(makes sense for struts I guess).
The bit I really hate is having to create so many form beans and dto beans and getting the getter and setter names matching the request parameters. For each JSP there is (in my app at least) an Action class, a form bean, 1 or 2 dto beans, and a service class to write. I feel much pain! (specially coming from perl)
I do have to agree with Graham though, Java (or j2ee) does have its place, but I have always believed in using tools appropriate for the job or situation. If my webapp was a banking app used by thousands of people a day this architecture would have been a better choice.
PH: 01144 1225 708225 • FAX: 01144 1225 899360 • EMAIL: firstname.lastname@example.org • WEB: http://www.wellho.net • SKYPE: wellho