on 5/17/01 12:23 AM, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
> On Thu, 17 May 2001, Christopher Kirk wrote:
>
>>
>>> 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. It would be beneficial to compile JSP straight to Java,
>> complete with debugging information included in the class file.
>
> Yes, debugging is a problem in the current jasper implementation. One
> solution, as you mentioned, is to "hack" the class to include line numbers
> that match the JSP file ( the line number is an annotation in the class ).
>
> There is another solution - to generate the map ( java line number ->
> JSP source line number). This is exactly how the .class annotation works,
> mapping bytecode to java source number. And will allow you to see both
> informations, and it's quite clean.
>
> I'm not an expert in debugging, but that sound like a reasonable solution.
> You'll have to wait a bit for the implementation - I'm still fighting
> with cleaning and merging the runtime.
>
> Costin
It is a hacky solution to a problem that shouldn't exist in the first place
because the technology was designed poorly to begin with.
-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>
