Answer inline:
> -----Original Message-----
> From: Christopher Kirk [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, May 17, 2001 3:17 PM
>
> >From my view, the problem with JSP->Java->Class isn't performance its
> debugging. JSP is hard to work with when you make a mistake, very
> often the
> error message is less than helpful. A very large step in improving this is
> by making the line number given by the stack trace match the line
> numbers of
> the JSP page. This currently is not the case because of the intermediate
> step of a java file.
You still can take a look at the intermediate java file to understand what
is going on. It is not trivial, but at least it makes clear if the bug is in
your code or on Jasper's.
Anyway, Jasper sure could probably be improved to give good enough
information
about JSP location of the source of an exception... and you could help
implementing that.
> It would be beneficial to compile JSP
> straight to Java,
> complete with debugging information included in the class file.
There are two problems with that approach:
1) The technical complexity of such project (even using tools like BCEL);
2) Then it would be harder for you to find out if an exception would be
caused by some bug in your code or in Jasper's code.
Anyway, you can also contribute to such thing. Some pointers that can
help you starting:
- You can find the above referred BCEL at
http://bcel.sourceforge.net/
- You can check Rhino Javascript's compiler on how do they directly
compile something (javascript in this case) into Java Bytecode:
http://www.mozilla.org/rhino/
- Maybe Go's Tea template compiler would be a closer match for JSP:
http://opensource.go.com/
Have fun,
Paulo Gaspar
>
> - Chris.
>
> ...............
