Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Cancel
- Home
- :
- About MichaelLundin
MichaelLundin
New Contributor II
since
07-04-2014
11-11-2020
11
Posts created
0
Kudos given
0
Solutions
1
Kudos received
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
My Ideas
(0 Idea Submissions)Latest Contributions by MichaelLundin
|
POST
|
Kelly, Thanks for the reply, and the explanation of the differences. Your suggestion of the addition of the corsEnabledServers works great, though, in fact, we found that we didn't really need the call we had to the xhrPlugin after all, so we have removed that. Thanks much, Mike
... View more
01-14-2015
07:37 AM
|
1
|
0
|
189
|
|
POST
|
I would if I knew where to do that. I don't see a place on the tech support page. Am I missing something?
... View more
01-09-2015
02:24 PM
|
0
|
0
|
189
|
|
POST
|
Not really. I could with the first layers to be added, but there are other (more dynamically created) layers that might be added later, which would be after the call to addCrossSiteXhr. I'm going to see if there is an alternative to addCrossSiteXhr or if there's a way to make it work nicer with the layers. It does seem like something changed in the ArcGIS API at 3.12 with this behavior, as the dojo versions between 3.11 and 3.12 are the same.
... View more
01-09-2015
12:54 PM
|
0
|
2
|
792
|
|
POST
|
Okay, so I've identified the cause. I've attached an HTML file that will reproduce the problem I'm seeing. The page will fail to load the map as-is. It is related to using dojo's xhrPlugins.addCrossSiteXhr method. Before that method is used, layers work fine. After that method is used, layers fail. It looks like that is stripping away some XHR references from the AdapterRegistry that the layers don't like having removed. If you change the version to 3.11, you'll still get an error in the JavaScript console, but the map will function. That was the part I was missing. In our full application, it looks like after some widgets are initialized, but before the page is fully loaded, we're using this method to allow for push notifications. Any layers created after that section of code would fail to load, anything before that section worked fine. If I remove that call, the application functions. Now to figure out how to work around it.
... View more
01-09-2015
12:44 PM
|
0
|
0
|
792
|
|
POST
|
Jeff, Correct, changing from 3.12 to 3.11 allows the application to run as usual, as does using 3.9. However, a simple test page that creates a map and adds a layer also works in 3.12 (using the same dojoConfig). To answer your other questions: 1. I am using just http. 2. I do not specify a baseUrl in the dojoConfig. 3. async is set to false in the dojoConfig
... View more
01-09-2015
10:25 AM
|
0
|
0
|
792
|
|
POST
|
And, also, if I switch back to the older JavaScript API (3.9 or 3.11), things work fine.
... View more
01-09-2015
08:56 AM
|
0
|
0
|
792
|
|
POST
|
Jeff, I wondered about that, too, but have checked to make sure that the require statements line up with the aliases. Also, in what confuses me the most, in my JavaScript file that initializes things, if I create the layer in a function early in the process, the layer is created without error. However, in another function (in the same JavaScript file, and the same set of requires/aliases) that gets called later in the lifecycle, the layer gets created with the loadError.
... View more
01-09-2015
08:54 AM
|
0
|
0
|
792
|
|
POST
|
I'm working on upgrading to the 3.12 version of the ArcGIS JavaScript API, and I'm hitting a bit of a snag. If I create a separate page and add a layer to a map everything works fine, so I know I have the API set up correctly. However, in my application, there comes a point where if I create an ArcGISTiledMapServiceLayer, it is immediately created with a loadError of "Error: no match found". The error occurs before the layer is added to the map (and even if it's never added to the map). I'm trying to create the smallest possible set of code for reproducing the problem, but haven't been able to isolate where it's happening. I apologize for not including any code samples, due to that, and will continue to try and get to a point where I can. More what I'm wondering is if anyone has hit this error before, and what it might mean. To make sure it wasn't my layer that was causing the problem, I have used multiple layers and I am currently trying with one of the ESRI base layers: var layer = new ArcGISTiledMapServiceLayer('http://services.arcgisonline.com/ArcGIS/rest/services/World_Topo_Map/MapServer'); Using Fiddler, I've also noticed that when I do this, no http request is made to the endpoint. Any help on this would be greatly appreciated. Thanks.
... View more
01-09-2015
08:21 AM
|
0
|
12
|
5677
|
My kudoed posts
| Title | Kudos | Posted |
|---|---|---|
| 1 | 01-14-2015 07:37 AM |
Activity Feed
- Got a Kudo for Re: Layer loadError with JavaScript 3.12 API. 01-15-2015 09:43 AM
- Posted Re: Layer loadError with JavaScript 3.12 API on ArcGIS REST APIs and Services Questions. 01-14-2015 07:37 AM
- Posted Re: Layer loadError with JavaScript 3.12 API on ArcGIS REST APIs and Services Questions. 01-09-2015 02:24 PM
- Posted Re: Layer loadError with JavaScript 3.12 API on ArcGIS REST APIs and Services Questions. 01-09-2015 12:54 PM
- Posted Re: Layer loadError with JavaScript 3.12 API on ArcGIS REST APIs and Services Questions. 01-09-2015 12:44 PM
- Posted Re: Layer loadError with JavaScript 3.12 API on ArcGIS REST APIs and Services Questions. 01-09-2015 10:25 AM
- Posted Re: Layer loadError with JavaScript 3.12 API on ArcGIS REST APIs and Services Questions. 01-09-2015 08:56 AM
- Posted Re: Layer loadError with JavaScript 3.12 API on ArcGIS REST APIs and Services Questions. 01-09-2015 08:54 AM
- Posted Layer loadError with JavaScript 3.12 API on ArcGIS REST APIs and Services Questions. 01-09-2015 08:21 AM
Contact Me
| Online Status |
Offline
|
| Date Last Visited |
11-11-2020
02:24 AM
|
Latest Tags
No tags yet