- This topic has 4 replies, 2 voices, and was last updated 20 years, 7 months ago by
.
-
Posts
-
I have a series of Java projects with different versions of my source tree, and a single web project. The reason for this layout is my source control system is not structured very well, and can’t easily be mapped to a web-app. I use Ant to build jars and move source code to the web app from one of my Java projects to the web project as needed. From the web project I deploy to my JRun installation using MyEclipse.
The problem I have is that it appears that while debugging in my J2EE server (JRun 4) the source files are pulled from one of the Java projects rather than the web project.
Can you tell me what the algorithm is for determining which source file is loaded into the debugger when I am running JRun under eclipse debugging? Am I possibly missing something in my web project configuration?
Are you asking about Java Class file sources, or JSP pages? Java class file sources are looked up using standard Eclipse debugger method, by searching your “Source” dirs of all open projects during debugging. JSP debugging is done via our source locator that is part of ME and hooked into the debugging process when you start your app server from ME.
I am concerned about java class source files. Since you mentioned that it is determined by the Eclipse default mechanism, I’ve been able to verify what has been going on by opening and closing projects. That is a big help already.
When you are debugging a JRun server launched through myEclipse, if you right click on the JRun4Server itme in the debug window in the debugging perspective you gain access to a ‘modify and launch’ tabbed dialog that allows you to make changes to the source search path. Is it possible to use this to modify the source search path for a jrun debugging session? Or is this created on-the-fly through myEclipseIDE?
