Take the 2-minute tour ×
Geographic Information Systems Stack Exchange is a question and answer site for cartographers, geographers and GIS professionals. It's 100% free, no registration required.

My application displays an Esri map, by accessing the Esri public sampleserver. I use Esri dojo API for this purpose. The Esri dojo I use is of version 1.6 and is locally installed (as a war) on my server. It's important to say that the rest of my dojo code is an older dojo version (1.3.2).
I use Firefox 3.6 and the strange thing is, I sometimes get a "Could not load cross-domain resources" message (at about 10% of my attempts). This problem happens more often on another pc (Firefox 3.6 as well): at about 80% of my attempts. It is usually (but not necessarily) solved after clearing Firefox cookies and cache.
Now, I know the code is ok, as I can see the map in most of my attempts. However, I can't figure out why it sometimes fails on my browser, and why the other browser almost constantly fails.
What do you think? What could be the cause for it?

share|improve this question
    
According to this blog, I should be able to see the crossdomain.xml file loaded when my browser succeeds on displaying the map, but I can't see it - perhaps this implies on the problem? –  gamadon Aug 10 '11 at 10:55
2  
have you tried testing your App with Firebug? Using the 'Net' tab, you should see all the requests and should be able to see which one is failing. That will help in narrowing down the problem. –  Devdatta Tengshe Aug 10 '11 at 13:59

1 Answer 1

Dvedatta, I did what you suggested and installed firebug on that browser in order to view the net tab.
Surprisingly, installing firebug solved the problem: the map started appearing at about 90% of my attempts, just like in the first pc I tried. In my opinion, the reason for the failures is the fact that the Esri server is remote, and the map load delays due to networking issues. I think that firebug delays the page load and therefore the map has enough time to load too. I think that a permanent solution would be changing the browser's timeout programmatically.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.