For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 4 replies, 3 voices, and was last updated 21 years, 4 months ago by
.
-
Posts
-
I am using MyEclipse 3.8 beta 1 with Eclipse 3.0 RC1, and BEA WLS 8.1 sp2 on Windows XP.
I created an Enterprise Application Project, that contains a webapp with a simple servlet. (eg. com.lcw.servlet.HelloServlet). I put a breakpoint in the servlet and everything was fine.
Then I created a WebApp Project, and created another simple servlet that has the same name, but slightly different behavior. So this servlet is also named com.lcw.servlet.HelloServlet. I added a breakpoint to it as well.
When I invoke each servlet in a browser, I can see the distinctive behavior of each servlet. However, the debugger always stops at the break point in the first servlet. I can’t make it stop in the second servlet.
Is there a way to make the debugger stop at the break point in the second servlet?
Thanks.
Leon Webster
Leon,
If you change the names to “HelloServlet1” and “HelloServlet2” does the behavior correct itself? Its possible that having the same name is screwing up the App Server Location > Eclipse Location breakpoint translation.If I change the name, the behavior corrects itself. But this still seems like a bug to me (although not a very serious bug). Thanks.
Leon
Leon let me check on this and see if its an ambiguity comming from the server or with the ME debugger.
Leon,
If I change the name, the behavior corrects itself. But this still seems like a bug to me (although not a very serious bug).
The problem is that when we communicate with the remote JVM, the reference information for the class that hit a breakpoint is simply it’s fully qualified name. Unfortunately, this does not contain project information so if you have multiple classes with the same fully qualified name in open projects, then the debugger can become confused. One way around this is to temporarily close the project that you’re not actively debugging. So yes, this is definately an undesirable behavior but one for which we haven’t been able to find a good solution since the server could be executing code from any or all of your projects at any point in time. Sorry for the confusion.
