[slackorama]

Howdy —

I can’t seem to get my breakpoints recognized in jetty 4.2.20. breakpoints in classes work fine but not in JSP’s. I’m running it under Windows XP on Eclipse 3.1.0 Build 200412162000 and am running MyEclipse 3.8.4. My Jdk is 1.5.0. Both eclipse and myEclipse are fresh installs. The JSP I’m trying to debug is using JSTL. Everything about my eclipse install is default. MyEclipse is the only plugin I’ve installed.

Thanks for the help and let me know if you need more info.

[Riyad Kalla]

Eclipse 3.1.0 Build 200412162000 and am running MyEclipse 3.8.4

TIP: Make sure you are using MyEclipse 3.8.4 BETA for 3.1

I can’t seem to get my breakpoints recognized in jetty 4.2.20

Do you have Jetty setup to launch in debug mode? When you add the breakpoint in your JSP page AND Jetty is running, does the breakpoint have a little checkmark in the round bubble? Are you sure youare using the MyEclipse jSP EDitor? (right click on JSP File > Open With > MyEclipse JSP Editor)

[slackorama]

Thanks for your reply.

Yep, I’ve got 3.8.4-BetaFor3.1 Buld 200501171200-3.8.4-BetaFor3.1 running.

Jetty is set to launch in debug mode via the -DDEBUG arg to the JVM.

The breakpoint does not have a checkmark in it but then neither do the breakpoints in servlets I’m debugging and those halt the process just fine.

Positive I’m using the JSP Editor. Everytime I open a JSP after a restart, I get the trial expries in less than 30 days warning from ME. And I also did what you listed above just to be extra sure.

[Riyad Kalla]

Jetty is set to launch in debug mode via the -DDEBUG arg to the JVM.

Actually switch to the ‘Launch’ subnode under the Jetty settings and make sure the radio button is set to “Debug”, and remove your -DDEBUG argument for now.

[slackorama]

Sorry, I forgot to mention that it’s already enabled in the pref.

[Riyad Kalla]

Can you try and do a test setup of Eclipse 3.0.1 SDK and MyEclipse 3.8.4, I want to determine if this is a bug with the BETA or a problem with ME/Jetty.

[Author]

Posts