URL linking to maps fail poorly when a layer is no longer available

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Create a link to a map containing several layers.
2. Rename one layername in the WMS source and update the data source and client.
3. Try to load the link to the map containing the renamed layer.

An easy way to reproduce this is to simply create a link to a map then modify 
the link to change the name of a layer to a non-existent one.

What is the expected output? What do you see instead?
The AtlasMapper client should ideally load the renamed layer and show it as 
broken in the layer list. This way the user would at least know which layer has 
been changed or removed. Instead all that is shown is the error message:

 "The application has failed to load the requested layers"

and none of the other layers are loaded.

What version of the product are you using? On what operating system?
Version 1.3, Linux

Please provide any additional information below.

Original issue reported on code.google.com by eric.law...@gmail.com on 22 Apr 2013 at 1:53

[GoogleCodeExporter]

TODO: Load available layers and give a list of layers that could not be loaded 
in a warning window.

Original comment by lafond.g...@gmail.com on 23 Apr 2013 at 4:05

• Changed state: Accepted

[GoogleCodeExporter]

Fixed in 1.4

The application was intended to work as expected, but there is one case that I 
haven't though of. When a layer can not be loaded, the application request that 
layer alone again. The server receive the request, can not load it and return a 
failure. OpenLayers execute the failure function which stop everything. I fixed 
it by supplying the same function for success and failure, and, at the end, if 
some layers could not be downloaded, I simply show an error message with the 
list of erroneous layers in an alert. The valid layers are now loaded in the 
map as expected.

Original comment by lafond.g...@gmail.com on 12 Jul 2013 at 6:16

• Changed state: Fixed
• Added labels: IssueClosed-1.4