[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [platform-debug-dev] Debug options.
|
Kris,
It is not impossible to do JSP source level debugging. The WSAD 4.0 GM
release supports debugging JSPs at the source level when using Websphere.
If you are trying to get JSP debugging to work with Tomcat, you will have
to talk to the Tomcat team about getting the classfile mangling into the
JSP page compiler.
jkca
"N V S Rama Krishna"
<ram_kri@xxxxxxxxx> To: <platform-debug-dev@xxxxxxxxxxx>
Sent by: cc:
platform-debug-dev-admin@e Subject: Re: [platform-debug-dev] Debug options.
clipse.org
11/30/2001 01:32 AM
Please respond to
platform-debug-dev
Cant we take help of the editor thaz built inside the WSAD ?
Is JSP source level debuging impossible, if so please throw some light on
the justification.
Thanks in advance.
Regards,
kris
----- Original Message -----
From: <Jed_Anderson@xxxxxxx>
To: <platform-debug-dev@xxxxxxxxxxx>
Sent: Monday, November 26, 2001 1:04 PM
Subject: Re: [platform-debug-dev] Debug options.
>
> The debugger does not support JSP source level debugging "out of the
box".
> However, it is possible to implement JSP source level debugging on your
> own.
>
> To support debugging of any language that gets compiled to Java classes
you
> must provide the following:
>
> 1. An editor for the language.
> 2. A tool that mangles the debug information in the .class file. The
debug
> information should point to the line numbers in the original source.
> Usually, the debug information contains references to the line numbers in
> the intermediate Java source. This tool must be run after every compile
of
> the source.
> 3. A source locator: the source locator takes a stack frame and returns
an
> object that can be used as input to the editor
> 4. A launcher that understands how to start a program written in your
> language. Currently, it must use the PatternDebugTarget when registering
> with the debug plugin (rather than the JDIDebugTarget).
> 5. The ability to set breakpoints in your editor. You ask
> PatternBreakpointFactory to create a new pattern breakpoint on a file,
line
> & with a given pattern. The pattern you supply is matched against the
name
> of the classfiles that are loaded. Currently it is a basic algorithm, we
> simply check to see that the fully qualified name of the class starts
with
> the given pattern.
>
> In the case of JSPs it's a little harder. JSPs are compiled by the
> application server, so your post-processing of the classfiles (as
required
> by #2) must be built into the server. Also, launching is a bit more
> confused because it requires you to start your server (or restart your
> application).
>
> jkca
>
>
>
>
> "N V S Rama Krishna"
> <ram_kri@xxxxxxxxx> To:
<platform-debug-dev@xxxxxxxxxxx>
> Sent by: cc:
> platform-debug-dev-admin@e Subject:
[platform-debug-dev] Debug options.
> clipse.org
>
>
> 11/26/2001 04:06 PM
> Please respond to
> platform-debug-dev
>
>
>
>
>
> Hi,
> I would like to know if we can step into JSPs using the current
Debugger
> (The plugin that gets shipped )? To what extent it is possible. I
> personally think its not possible but just want to confirm if I am
missing
> anything here. Shall be thankful if somebody can throw light on this
issue.
> Thanks in advance.
>
> Regards,
> Kris
>
>
>
> _______________________________________________
> platform-debug-dev mailing list
> platform-debug-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/platform-debug-dev
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
_______________________________________________
platform-debug-dev mailing list
platform-debug-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-debug-dev
