...suggested we just copy the old xml into the new but how do I know what exactly to copy?
I am in the process of migrating my modifications from 2.1 to 2.2, and for every code module and configuration file I wonder if there are any changes at all to the new version. If I knew there were no changes I could just use my previous file, but I'm going through the tedious process of finding all my modifications and editing them into the new files. At the risk of asking too much, would it be too difficult to put a date and/or version number in each file (.xml, .mxml, .as) so we could save some time with the migration? Or perhaps provide a list of changed or unchanged files (whichever is easier)?Thanks,Marc
Cynthia (and others), to migrate your 2.1 viewers: If working with the source code:Download the new viewer.Copy your modified xml's file over to the new viewer.Review What's new to see if there's something new you want to take advantage of.For changes made in the mxml files ... depends. If it was something that was fixed, then do nothing. For fixes that you want to migrate over, the best way is probably to compare that specific mxml and integrate your changes with ours.
The overviewMapWidget doesn't work in this new release because it only displays a blank window
Brian,We'll look at supporting wkid on the layer tag for type "wms" in a future release.As a work-around, you can try this:<layer label="NOAA Infrared Satellite" type="wms" visible="false" visiblelayers="RAS_GOES_I4" url="http://nowcoast.noaa.gov/wms/com.esri.wms.Esrimap/obs?srs=EPSG:102113"/>This seems to work but is service dependent. Any additional url parameters are sent by the API in its requests to the servcie. The API will overwrite any it uses, but since it's case-sensitive and it uses SRS, then both srs and SRS will be sent and in this instance, the service seems to look for the srs parameter first.
Cynthia (and others), to migrate your 2.1 viewers:A) If working with the compiled version:Download the new viewer.Copy your modified xml's file over to the new viewer.Review What's new to see if there's something new you want to take advantage of. If working with the source code:Download the new viewer.Copy your modified xml's file over to the new viewer.Review What's new to see if there's something new you want to take advantage of.For changes made in the mxml files ... depends. If it was something that was fixed, then do nothing. For fixes that you want to migrate over, the best way is probably to compare that specific mxml and integrate your changes with ours.
The wkid goes on the map tag, but it may not be needed. Make sure the visiblelayers match the available layer names. You may need to use a tool like HttpFox to see what the request/responses are.
Hi dpaddock,I made the change in config.xml on basemaps:<layerlabel="axa"type="wms"visible="true"visiblelayers="0,2"wkid="EPSG:31600"url="http://localhost:8080/geoserver/wms"/>and i received a blank page..ESRI logo si loaded and staying on Transferring data from localhost..i have a crossdomain.xml if help.
<Layer queryable="0" opaque="0" cascaded="0"> <Name>hypsography</Name> <Title>Hypsography</Title> - <Abstract> The Hypsography layer represents elevation points and continuous lines formed by peaks of equal altitude used to describe the topography. Elevation of points and lines is always calculated from mean sea level. </Abstract> <SRS>EPSG:4269</SRS>
SecurityError: Error #2048: Security sandbox violation: http://465793h/FlexViewer2.2/index.swf cannot load data from http://wms.ess-ws.nrcan.gc.ca/wms/toporama_en?VERSION=1.3.0&REQUEST=GetCapabilities&SERVICE=WMS. at Function/com.esri.ags.layers:WMSLayer/private:loadCapabilities/com.esri.ags.layers:myFaultFunction() at mx.rpc::AsyncResponder/fault() at mx.rpc::AsyncToken/http://www.adobe.com/2006/flex/mx/internal::applyFault() at mx.rpc.events::FaultEvent/http://www.adobe.com/2006/flex/mx/internal::callTokenResponders() at mx.rpc::AbstractInvoker/http://www.adobe.com/2006/flex/mx/internal::dispatchRpcEvent() at HTTPOperation/http://www.adobe.com/2006/flex/mx/internal::dispatchRpcEvent() at mx.rpc::AbstractInvoker/http://www.adobe.com/2006/flex/mx/internal::faultHandler() at mx.rpc::Responder/fault() at mx.rpc::AsyncRequest/fault() at DirectHTTPMessageResponder/securityErrorHandler() at flash.events::EventDispatcher/dispatchEventFunction() at flash.events::EventDispatcher/dispatchEvent() at flash.net::URLLoader/redirectEvent()
Přihlášení členové mohou přispívat, sledovat aktualizace a další. Jste tu noví? Zaregistrujte si bezplatný účet.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.