[MadEagle]

Hi all,

I am confused. I have two JSPs in the same project and even in the same directory. In one of the JSPs a breakpoint is honored and in the other it is ignored. Can somebody explain this? Any idea?

I noticed that the working breakpoint has a small check mark superimposed over the blue dot when I set it and the not working breakpoint shows only the blue dot. The only difference I can think of between the two JSPs is that the working one is actually printing out HTML while the other just does some update on the database and then redirects.

– System Setup ——————————-
Operating System and version: Win XP + SP 1
Eclipse version: 2.1.2
Eclipse build id: 200311030802
Fresh Eclipse install (y/n): y
If not, was it upgraded to its current version using the update manager?
Other installed external plugins: XMLBuddy 2.0.2
Number of plugins in the <eclipse>/plugins directory: 67
MyEclipse version: 2.7RC2
Eclipse JDK version: 1.4.2_03
Application Server JDK version: 1.4.2_03
Are there any exceptions in the Eclipse log file? y

– Message Body ——————————-

Hm, actually there is one exception in the log that I didn’t notice before.

!ENTRY com.genuitec.eclipse.ast.deploy.core 1 1 Feb 10, 2004 16:54:34.846
!MESSAGE Unable to add Deployment BuildSpec
!STACK 1
org.eclipse.core.internal.resources.ResourceException: Resource is out of sync with the file system: /IT-Controlling/.project.
    at org.eclipse.core.internal.localstore.FileSystemResourceManager.write(FileSystemResourceManager.java:637)
    at org.eclipse.core.internal.resources.File.internalSetContents(File.java:238)
    at org.eclipse.core.internal.resources.File.setContents(File.java:274)
    at org.eclipse.core.internal.localstore.FileSystemResourceManager.internalWrite(FileSystemResourceManager.java:259)
    at org.eclipse.core.internal.resources.Project.writeDescription(Project.java:906)
    at org.eclipse.core.internal.resources.Project.setDescription(Project.java:807)
    at org.eclipse.core.internal.resources.Project.setDescription(Project.java:829)
    at com.genuitec.eclipse.ast.deploy.core.DeploymentNature.configure(Unknown Source)
    at org.eclipse.core.internal.resources.NatureManager$1.run(NatureManager.java:134)
    at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:1006)
    at org.eclipse.core.runtime.Platform.run(Platform.java:413)
    at org.eclipse.core.internal.resources.NatureManager.configureNature(NatureManager.java:148)
    at org.eclipse.core.internal.resources.NatureManager.configureNatures(NatureManager.java:192)
    at org.eclipse.core.internal.resources.Project.basicSetDescription(Project.java:49)
    at org.eclipse.core.internal.resources.Project.setDescription(Project.java:803)
    at org.eclipse.core.internal.resources.Project.setDescription(Project.java:829)
    at com.genuitec.eclipse.j2eedt.core.J2EEProjectUtil.addNatures(Unknown Source)
    at com.genuitec.eclipse.ast.deploy.core.DeploymentManager.addDeploymentNature(Unknown Source)
    at com.genuitec.eclipse.ast.deploy.core.DeploymentManager.addDeployment(Unknown Source)
    at com.genuitec.eclipse.ast.deploy.core.DeploymentManager.loadFromPreferences(Unknown Source)
    at com.genuitec.eclipse.ast.deploy.core.DeploymentManager.init(Unknown Source)
    at com.genuitec.eclipse.ast.deploy.core.DeploymentManager.<init>(Unknown Source)
    at com.genuitec.eclipse.ast.deploy.core.DeploymentManager.getDefault(Unknown Source)
    at com.genuitec.eclipse.ast.deploy.core.ui.dialog.DeploymentManagerDialog.updateDeploymentsViewerForProject(Unknown Source)
    at com.genuitec.eclipse.ast.deploy.core.ui.dialog.DeploymentManagerDialog.createDialogArea(Unknown Source)
    at org.eclipse.jface.dialogs.TitleAreaDialog.createContents(TitleAreaDialog.java:131)
    at org.eclipse.jface.window.Window.create(Window.java:302)
    at org.eclipse.jface.window.Window.open(Window.java:552)
    at com.genuitec.eclipse.ast.deploy.core.ui.action.DeploymentMgmtActionDelegate.runWithEvent(Unknown Source)
    at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:241)
    at org.eclipse.ui.internal.WWinPluginAction.runWithEvent(WWinPluginAction.java:207)
    at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:456)
    at org.eclipse.jface.action.ActionContributionItem.handleWidgetEvent(ActionContributionItem.java:403)
    at org.eclipse.jface.action.ActionContributionItem.access$0(ActionContributionItem.java:397)
    at org.eclipse.jface.action.ActionContributionItem$ActionListener.handleEvent(ActionContributionItem.java:72)
    at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
    at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
    at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1402)
    at org.eclipse.ui.internal.Workbench.run(Workbench.java:1385)
    at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:858)
    at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at org.eclipse.core.launcher.Main.basicRun(Main.java:291)
    at org.eclipse.core.launcher.Main.run(Main.java:747)
    at org.eclipse.core.launcher.Main.main(Main.java:583)
!ENTRY org.eclipse.core.resources 4 274 Feb 10, 2004 16:54:34.846
!MESSAGE Resource is out of sync with the file system: /IT-Controlling/.project.

Any idea where that comes from and if it is at all related with my problem?

Thanks, MadEagle
undefined

[etornick]

I read somewhere in the myeclipse documentation that the checkmark meant that the classfile that the breakpoint is in has been loaded by the classloader.

This may not solve your problem but it was one of your questions.

Ed

[Scott Anderson]

MadEagle,

Ed is correct. Eclipse places the checkmark on the breakpoint when the class for the JSP is loaded into the remote JVM. Do you have a JSP with an identical name in any other folders or projects? It might be confusing the debugger as to which source is being loaded. Just a thought.

[MadEagle]

OK, that would explain the behaviour, but the name of both JSPs are unique application wide (and since this is the only application running also application server wide). I will look further into this matter. Any other ideas anybody?

MadEagle

[Scott Anderson]

Actually, it may or may not explain the behavior. To verify easily, you can temporarily close any other projects that
contain a JSP with the same name as the one giving you a problem. If unsetting and resetting the breakpoint then causes
debugging to work properly on the problematic JSP, we definately know what the issue is.

[Author]

Posts