[Mork]

Hi,

When setting a break point in an index.jsp, when the debugger starts it opens another index.jsp from another project (as well as the index.jsp I have the breakpoing on in the current project).

I did have a breakpoint in the other Web project, but it wasn’t the index.jsp page I had open in the debugger or the Webpage (index.jsp) I started in the browser.

Still MyEclipse opened it too and actually wanted to debug it instead of the index.jsp I opened and had the breakpoint of interest on.

I tried cleaning the project I was debugging, but that didn’t help.

When I cleared the breakpoint in the index.jsp that came up by mistake and tried it again, MyEclipse brought up another index.jsp from yet another WEb project.

I cleared all the breakpoints in the breakpoint perspective, but it keeps trying to debug the wrong index.jsp. In fact, it opens the index.jsp that is incorrect right next to the one I’m trying to debug.

If this isn’t enough detail, please let me konw.

This is driving me nuts!

Thanks.

– M

[Mork]

To verify this behavior (bug?) just have two Webprojects with index.jsp files you’ve opened recently. I think the problem may relate to the Least Recently Used method you see at the bottom of the file menu.

I think you should try to debug the first index.jsp, clear the break point and close that project.

Then open the other index.jsp in the other project (I am also opening another class as well). Set a break point on the index.jsp and start the browser.

I get BOTH index.jsps open in MyEclipse even though only one was open when I started the browser.

This is very strange but reproducible!!!

HELP!!!!

[Riyad Kalla]

Please close the project with the conflicting index.jsp file. One benefit of how debugging works is that it will traverse multiple projects so if you deployed a project that depends on 2 other projects, debugging will work across those project boundries… the problem, as you found, is that when projects have same-named files, the source locater gets confused as to which one you want, especially with JSP pages where there is no unique package definition. The work around (And solution) is to close any offending projects during debugging that you don’t need. Sorry for the inconvenience.

[Mork]

Thanks very much for your reply.

The other project with the index.jsp wasn’t “open”, but it had been earlier.

I tried everything I knew how to do to keep that other index.jsp file from opening.

This sounds like a bug or at least something that needs to be looked at further.

— M

[Riyad Kalla]

Mork,
I don’t follow… are thinkgs working now, or still not working?

If still not working, can you verify this for me:
Stop your app server, close all your projects, reopen the 1 project you want, start your app server, set a break point, try and hit it… from what you are saying ti sounds like now the breakpoint in the *closed* project’s file is hit? I don’t follow… AFAIK this is not supported by Eclipse (opening a file in a closed project).

[Mork]

Maybe I’m not sure what it means to have a closed project.

I closed MyEclipse several times and when I was debugging only the single index.jsp would have a breakpoint in it and be the only index.jsp (the one I wanted to debug) open.

But, when the browser hit that index.jsp, up pops another index.jsp, for another project, into the debugger.

Could the other project be open? If I go to File… all the close options are closed when I first start MyEcliplse so how could another project be open when I just open the single index.jsp in the debugger.

I realize I may be doing something wrong, I just don’t see what it is.

Could this possibly be a bug?

I just tried it again and it KEEPS DOING IT!!!

(I’ve been able to get around this problem by simply going to a class the index.jsp uses, but if I really needed to debug the index.jsp, I’d be out of luck).

If you like I could send you a Camtasia movie (AVI file) showing you the second index.jsp popping up when it wasn’t listed in any breakpoints.

Don’t you guys have some type of program that can check the internals of what the debug perspective is going to do when it opens?

Something is definitely wrong.

Look forward to your reply.

— M

[Riyad Kalla]

Mork,
All of your projects in Eclipse should be shown to you in a tree view, on the left side of your screen in either the Package View (default) or Navigator View. If you right click on any of the root nodes of the tree (every root is a project) you should see an option “Close project” and subsequently “Open project” assuming the project is closed.

You don’t need to send us a movie IF infact you do have multiple projects with index.jsp open at the same time; we are aware of the behavior. However if you do infact have all your projects closed, and the wrong one is tsill getting oepned, then yes sending a movie of the situation might be helpful. Can you clarify that you are infact closing the projects first? Please check Eclipse help if you need further instruction on how to do this.

[Mork]

Nope, my fault.

I did in fact have the projects open.

I didn’t realize that having the “+” in the treview meant they were open after I restarted Eclipse.

Thank you very much for your terrific help!!!!

Best Regards,

–M

[Riyad Kalla]

No problem, glad its working now.

[Author]

Posts