[samueldoyle]

So I can load a page and get a list of all the javascript files the first time. If I close your browser or try to start a new session the javascript files are never presented in the script inspector again although I can start a debugging session. It appears the Web 2.0 / AJAX portion of your product is not ready for primetime.

[Riyad Kalla]

The JS files are loaded when the debugging session is started. Are you simply closing the window, or are you stopping the debug session before starting the next one?

[samueldoyle]

Yes, I’m terminating the debugging session. I will then try to start a new debugging session, the scripts do not reload and are not available in the inspector. If I try to set a bp in the file nothing happens, the thing just bombs out. The free firefox debugger appears more stable then you you have.

[Greg]

Do you have an example project or website where this occurs? If we can reproduce the error we can likely find a fix for it in the next release.

[harryajh]

I’m getting an identical problem to this, after a while (not been able to determine exact sequence yet!) the breakpoints just get ignored.

One way around it was to close eclipse, re-open, build & deploy app (on tomcat 6) again then try again – this worked once but not after, as samula says “the scripts do not reload and are not available in the inspector”

any ideas on this? – this was the reason I bought the Pro version but I may have to try FireFox debugger

thanks

harry

[Riyad Kalla]

As Greg mentioned, any sample sites you can provide where this happens will help us debug and fix this problem right away. On our own internal testing and just in general use creating tutorials and so on we haven’t seen this, but if we can get a test case that reproduces it, we’ll dig in.

[Author]

Posts