[DaftMule]

I have an annoying problem with MyEclipse 8 which is hopefully just down to a configuration setting somewhere.

I’m running a deployed project in tomcat and the error stack traces are written to the console window. All fine and dandy except for the fact that the hyperlinks to the class(es) throwing the errors take me to the compiled .class file rather than the source .java file. This is really annoying as I then have to manually open the .java source file and find the line in question.

If the class was in a jar included with the deployment then this is to be expected as the source wouldn’t be available. However, this is a class which is in the deployed app, not in a jar and I have the source open in my workspace.

Any ideas?

Installation details as follows:

*** Date:
Friday, 26 March 2010 09:12:50 o’clock GMT

** System properties:
OS=WindowsXP
OS version=5.1.0
Java version=1.6.0_13

*** MyEclipse details:
MyEclipse Enterprise Workbench
Version: 8.0
Build id: 8.0-20091120

*** Eclipse details:
MyEclipse Enterprise Workbench

Version: 8.0
Build id: 8.0-20091120

Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-showsplash
-launcher
C:\Program Files\Genuitec\MyEclipse 8.x Latest\myeclipse.exe
-name
Myeclipse
–launcher.library
C:\Program Files\Genuitec\MyEclipse 8.x Latest\../Common/plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.0.200.v20090519\eclipse_1206.dll
-startup
C:\Program Files\Genuitec\MyEclipse 8.x Latest\../Common/plugins/org.eclipse.equinox.launcher_1.0.201.R35x_v20090715.jar
-install
C:/Program Files/Genuitec/MyEclipse 8.x Latest
-vm
C:/Program Files/Genuitec/Common/binary/com.sun.java.jdk.win32.x86_1.6.0.013/jre/bin/client/jvm.dll

[Brian Fernandes]

This does work for us, with an externally configured Tomcat 6 instance. We tried run / debug and packaged / exploded deployment and it worked for everything.

What version of Tomcat are you running? Could you please paste the contents of your .classpath and .mymetadata files here?

[DaftMule]

I have worked out what the problem was. I was using a separate “tester” project to call the services in the deployed project. For some reason I had included the .jar of the deployed project in the “Java Build Path – > Library’s” of the tester project and, even though the src for that jar was set to the src of the deployed project in my workspace, it still seemed to want to show me the compiled .class files from the jar when clicking on the stack trace link in the console.

Have removed that .jar file from the tester project and it now links to the correct .java file from the stack trace in the console

The only slightly puzzling thing is that the jar file had it’s src attribute set yet it still refused to go to it….

[Author]

Posts