[Peter Pilgrim]

Hello Guy

This warning dialog has been bugging me since MyEclipse 6.5.

I do not have any JavaScript in my current Java EE 5 / JPA / Spring standalone project. Everytime I pres the “Debug” icon in the tool bar I am greeted with this dialog. The message is:

“Warning: You have chosen to debug a JavaScript application using a non-HTML file. For this file to work correctly, you most likely need to modify the URL field to be context of a deployed Web application before continuing with this debug launch.”

I repeat I have no JavaScript in my project at all. It is a standalone project, Maven single project with JPA and Spring Framework dependencies.

How do I disable this dialog box?

Thanks

[support-shalini]

Peter,
Clicking on debug would launch the last debug operation done. Can you first browse to your main class and select Debug As > javascript Application from the context menu, complete the debug cycle and then click on Debug from the toolbar?
Let me know if that helps.

[Peter Pilgrim]

Why do I have to do this? My application does NOT use JavaScript at all. It is a Java EE application using JPA and Spring. There is no JavaScript involved. I want to turn the JavaScript debug dialog off or disable. There must be a configuration option to do this.

[Brian Fernandes]

Peter, what version of ME are you using right now? What editor is active when you hit the debug button?

[pcoates]

This issue is driving me quietly insane.

I also am not using JavaScriptt, but when I hit the debug button on the top bar, the IDE apparently randomly decides whether or not to behave in the expected way. Sometimes I will get “You have chosen to debug a JavaScript application using a non-HTML file…” and sometimes I don’t. Often it will happen persistently, but by switching to a different view, say SVN or Database, I can jog it back into working correctly. Kicking the vending machine as it were. Occasionally it is so persistent that I have to restart the IDE.

I would be happy to completely disable anything having to do with JavaScript. This problem sometimes gets so bad that I have to stop using the debugger entirely and resort to System.out.println().

[support-swapna]

pcoates,

I could replicate it at my end. I will check with the dev team and get back with their suggestions.

[Brian Fernandes]

I agree this can be very frustrating and irritating behavior. Unfortunately we could not put this into the 9.0 GA release which is due today, but I am targeting a fix for the next release after this.

[Author]

Posts