For starters, you shouldn' try to compare "Perl CGIs"
to "JSPs". What you have to remember is that JSP is just a
a templating system for creating Java servlets easily.
If you want to compare it to something, compare it to a
perl templating system, something like
Mason is probably
comparable.
I write Java Servlets & JSPs at work, the "CGI.pm" of JSPs
are the HttpRequest and HttpResponse classes (and instance
of which is magically created for you) which have all of
the methods you would expect. The Chief Architect at my
company is no bone-head, he did a lot of performance
analysis of both Weblogic proxied through Apache & mod_perl,
assuming that people wrote "imperfect" JSPs & CGIs (ie:
not optimal code) and determined that the performance of
JSPs in Weblogic was pretty much the same as mod_perl.
He choose to go ahead with Weblogic &JSPs because he
thought it would be easier for people with very little
programming experience to write JSPs then to write perl
scripts. (NOTE: he didn't try any Perl templating systems.)
If everyone on your team has strong Java experience,
you might as well
stick with that. The meat of your work can be done in
support classes that won't be any different from any other
Java classes you've written, using JSPs to generate the HTML
should be relatively
trivial to pick up. Your whole team can probably learn the
syntax of JSP tags faster then you can get the remaining
guys of your team to learn Perl from scratch.
