- This topic has 1 reply, 2 voices, and was last updated 20 years, 1 month ago by
.
-
Posts
-
Not sure if this is my misunderstanding or a debugger error. I have two projects A and B both projects have a src folder with a package called com.test which contains one .java file. When I have both web projects deployed they both work fine calling the com.test.my.class which was built from the .java file. When I change project B’s my.java file to include another function and stop and start the JSP debugger it amazing brings up project A’s .java source and appears to use A’s .class file as well. The breakpoint however must be on Projects B’s my.java file in order to stop.
I believe that this is due to an alphabetical problem using A before B. My real project names are WebAppA and WebAppB. Or should I expect that duplicate named packages cannot be determinted by Tomcat and/or the Debugger? This would make sense from the standpoint that really only one VM exists in my configuration.
All Confused
ScotchyScotchy,
The problem is that the debugging information returned from the remote JVM includes only the fully qualified classname of the class to be debugged, but no project information. Since you have exactly the same class in multiple projects, the debug system can’t disambiguate the reference, so the first one found is used as the debug target. The only workarounds I know to this are to change the fully qualified path to one of the files, or to temporarily close one of the projects while debugging the other.
