You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Kent Tong <ke...@cpttm.org.mo> on 2004/10/05 06:03:19 UTC
Debug a Tapestry app in Eclipse
Hi,
I have the Sysdeo Tomcat plugin installed in Eclipse. I can
also use the debugger in Eclipse to step through the code
in a standard servlet app. For a Tapestry app, I can still set
a breakpoint and the execution does stop there but Eclipse
can't find the corresponding source file and thus can't
display the source. Any idea? Have you had any success in
doing this?
Thanks!
--
Kent Tong, Msc, MCSE, SCJP, CCSA, Delphi Certified
Manager of IT Dept, CPTTM
Authorized training for Borland, Cisco, Microsoft, Oracle, RedFlag & RedHat
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Debug a Tapestry app in Eclipse
Posted by kd...@kcp.com.
Actually, I am using Sysdeo without any problems under Tomcat 5.0 (but
have used 3.3, 4.0, 4.1, and 5.0). There is two keys. The first is
obvious, start Tomcat within Eclipse using Sysdeo's start (and stop and
restart) Tomcat buttons.
The second thing, very important, is making sure you are making the source
available. Go to
Window | Preferences
Tomcat | Source Path
Select all your servlet projects
And now you should be able to set break points, step throught, etc. Works
great for me and others around here.
Kevin
--
Kevin C. Dorff
IT Systems Engineer, Staff
National Nuclear Security Administrations Kirtland Operations
Operated by Honeywell Federal Manufacturing & Technologies, LLC
Phone: 505-844-3785
Fax: 505-844-3326
www.kcp.com
Howard Lewis Ship <hl...@gmail.com>
10/05/2004 12:38 PM
Please respond to
"Tapestry users" <ta...@jakarta.apache.org>
To
Tapestry users <ta...@jakarta.apache.org>
cc
Subject
Re: Debug a Tapestry app in Eclipse
That's my advice as well. JettyLauncher works great and debugging is
easy. Eclipse 3.0 is better because it doesn't complain all the time
about the fabricated classes (enhanced classes have no line number
table, and Ec 2.1 would complain each time the class was loaded).
On Tue, 5 Oct 2004 14:32:24 -0400, Kevin J. Menard, Jr.
<ni...@negativetwenty.net> wrote:
> On Oct 5, 2004, at 12:03 AM, Kent Tong wrote:
>
> > Any idea? Have you had any success in
> > doing this?
> >
> I've had no problem debugging Tapestry apps in Eclipse using Spindle &
> JettyLauncher. I did have all sorts of problems trying to use Sysdeo
> Tomcat though. I eventually just bit the bullet and used JettyLauncher
> and have been happy since.
>
> --
> Kevin
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
--
Howard M. Lewis Ship
Independent J2EE / Open-Source Java Consultant
Creator, Jakarta Tapestry
Creator, Jakarta HiveMind
http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Debug a Tapestry app in Eclipse
Posted by Howard Lewis Ship <hl...@gmail.com>.
That's my advice as well. JettyLauncher works great and debugging is
easy. Eclipse 3.0 is better because it doesn't complain all the time
about the fabricated classes (enhanced classes have no line number
table, and Ec 2.1 would complain each time the class was loaded).
On Tue, 5 Oct 2004 14:32:24 -0400, Kevin J. Menard, Jr.
<ni...@negativetwenty.net> wrote:
> On Oct 5, 2004, at 12:03 AM, Kent Tong wrote:
>
> > Any idea? Have you had any success in
> > doing this?
> >
> I've had no problem debugging Tapestry apps in Eclipse using Spindle &
> JettyLauncher. I did have all sorts of problems trying to use Sysdeo
> Tomcat though. I eventually just bit the bullet and used JettyLauncher
> and have been happy since.
>
> --
> Kevin
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
--
Howard M. Lewis Ship
Independent J2EE / Open-Source Java Consultant
Creator, Jakarta Tapestry
Creator, Jakarta HiveMind
http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Debug a Tapestry app in Eclipse
Posted by "Kevin J. Menard, Jr." <ni...@negativetwenty.net>.
On Oct 5, 2004, at 12:03 AM, Kent Tong wrote:
> Any idea? Have you had any success in
> doing this?
>
I've had no problem debugging Tapestry apps in Eclipse using Spindle &
JettyLauncher. I did have all sorts of problems trying to use Sysdeo
Tomcat though. I eventually just bit the bullet and used JettyLauncher
and have been happy since.
--
Kevin
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org