Performance

Why developers should wait for the .java file generation and compilation if JSP files can be interpreted? Will it actually make a difference in development time?

A correct answer would be — it depends. It depends on the type of the application, amount of code in JSP files, the stage of the application (development, maintenance, refactoring) and whether the developers switch to reading slashdot when they are forced to wait for a deployment for more than few seconds.

When considering a typical application using JSPs only as a view which is in development phase, using JSP Weaver will save your developers between 10 and 20 minutes a day. It may not seem a lot, but multiply the number by the number of developers in your company and by the hourly price of a developer and you will end up with pretty astonishing figures.

JSP Weaver performance has been tested in a wide variety of JSP projects as the primary JSP interpreting servlet for development. The current release has also been benchmarked with a set of different JSP files to the compare the performance of JSP Weaver to other JSP parsers.

JSP Weaver brings up to 50 times faster reload times with certain files. Regular speed up gain is around 10-20 times. You can always give the product a try and download the evaluation version.

* Average J2EE developers cost to the company per hour.