on 5/17/01 8:01 AM, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
> Ok Chris. Now I undertand.
> Working with JSP when I found that type of mistakes I went to see the .java
> generated. There I matched the line number so I could see which was the bad
> code. Then I had to go to the jsp to fix it.
> It is not the best of the world, but is that that bad?
If you think about *who* the target JSP audience is, Yes.
Do you expect page designers to figure out problems with line numbers by
going to look at the generated page in some temp directory somewhere? Gee, I
hope not.
More humor for you JSP "believers":
<http://www.theregister.co.uk/content/4/18996.html>
You may also wish to read a complete pile of bullshit here:
<http://java.sun.com/products/jsp/jsp-asp.html>
My favorite:
ASP Technology JSP Technology
------------------------------------------------------------------------
Reusable, Cross-Platform Components No JavaBeans, Enterprise
JavaBeans, custom JSP tags
------------------------------------------------------------------------
Security Against System Crashes No Yes
------------------------------------------------------------------------
Memory Leak Protection No Yes
------------------------------------------------------------------------
Scripting Language VBScript, JScript Java
------------------------------------------------------------------------
Customizable Tags No Yes
------------------------------------------------------------------------
Yea, JSP protects you from "memory leaks" and "System Crashes". Yea Right.
Oh yea, and ASP is "lacking" customizable tags...as if customizable tags is
a good thing?
JSP sucks.
-jon
--
If you come from a Perl or PHP background, JSP is a way to take
your pain to new levels. --Anonymous
<http://jakarta.apache.org/velocity/ymtd/ymtd.html>
