This post originated from an RSS feed registered with Agile Buzz by Dominik Wei-Fieg. Original Post: Chiming in: JSP - Innocence Lost Feed Title: Ars Subtilior Feed URL: http://typo.ars-subtilior.com/articles.rss Feed Description: Finest Handmade Code Random thoughts about agile software development as an art Latest Agile Buzz Posts Latest Agile Buzz Posts by Dominik Wei-Fieg Latest Posts From Ars Subtilior

Yesterday Angsuman Chakraborty wrote about his feelings concering JSP.

I totally agree with him. 7 to 8 years ago I was on several projects which used JSP. These projects ranged from one month with 2 developers to 1 year with 10+ developers. And they actually were fun to do.

Starting this year I was (and still am) involved in two projects which again used Java technology for the web frontend.

The first was using JSF. No real support for POST says all.

The current project is using plain JSP with Spring. I admit that Spring is a lot easier than EJB 2.1, but for me it still goes tha Java framework way of making difficult things possible but at the same time making easy, “default” behavior difficult.

Expression Language is something which was introduced to Java web development which I wouldn’t want to miss. But the whole setup of a JSP project using the current stack is, imho, too difficult. When Angsuman says that the current JSP technology is not usable for rapid prototyping he is right. I guess it will take most programmers between two days to a week to set up the infrastructure and build support for an JSP project.

OK, if you use tools for RAD, you might be faster, but I always like to know what is getting generated, just in case that it might not work as it should (which will happen, that is sure).

When the customer is not forcing me to use java for a web application, I would never use it. But then I guess I really have already departed.