Opened 17 years ago
Closed 17 years ago
#328 closed defect (fixed)
Fusion: error property in JSON object of mapLoaded is incomplete.
Reported by: | jng | Owned by: | pagameba |
---|---|---|---|
Priority: | medium | Milestone: | 2.0 |
Component: | General | Version: | |
Severity: | major | Keywords: | fusion |
Cc: | madair | External ID: |
Description
I've tried creating an ApplicationDefinition (Slate) out of one of our existing cemetery maps to see what it looked. When I loaded the map, it gave me this error
Fusion Error: Missing } in property list at /fusion/mapguide/MapGuide.js (line 193)
So I looked at that particular line in firebug, and it was a json object being eval'ed, so I reloaded the map again so I could trap the json output, and this is what I got from firebug (copy/pasted)
{sessionId:'0f952198-0000-1000-8003-000c292b5017_en_0A00053B0AFC0AFB0AFA',mapId:'Library://Cemeteries/Bridgewater/Maps/BridgewaterMap.MapDefinition',metersPerUnit:1,mapName:'BridgewaterMap',extent:[226822.35112645,5943821.3474294,227164.83574661,5944235.9071711],layers:[{propertyMappings:{},uniqueId:'1163a9cc-0000-1000-8005-000c292b5017',layerName:'TreePoints',layerTypes:[0],displayInLegend:true,expandInLegend:true,resourceId:'Library://Cemeteries/Bridgewater/Layers/TreePoints.LayerDefinition',parentGroup:'1163a9cc-0000-1000-8003-000c292b5017',legendLabel:'TreePoints',selectable:true,visible:true,actuallyVisible:false,editable:true,scaleRanges: [{minScale:1501,maxScale:100000000.0,styles:[{legendLabel:'',filter:'',geometryType:1,categoryIndex:0}]},{minScale:901,maxScale:1500,styles:[{legendLabel:'',filter:'',geometryType:1,categoryIndex:0}]},{minScale:361,maxScale:900,styles:[{legendLabel:'',filter:'',geometryType:1,categoryIndex:0}]},{minScale:100,maxScale:360,styles:[{legendLabel:'',filter:'',geometryType:1,categoryIndex:0}]}]},{propertyMappings:{},uniqueId:'1163a9cc-0000-1000-8006-000c292b5017',layerName:'MainTitle',layerTypes:[0],displayInLegend:true,expandInLegend:true,resourceId:'Library://Cemeteries/Bridgewater/Layers/MainTitle.LayerDefinition',parentGroup:'1163a9cc-0000-1000-8004-000c292b5017',legendLabel:'MainTitle',selectable:false,visible:true,actuallyVisible:true,editable:true,scaleRanges: [{minScale:0,maxScale:100000000.0,styles:[{legendLabel:'',filter:'',geometryType:1,categoryIndex:0}]}]},{ERROR: An exception occurred in FDO component. RDBMS: No current open database. An exception occurred in FDO component. RDBMS: No current open database. Exception occurred in method MgFdoConnectionManager.Open at line 862 in file d:\buildforgeprojects\mapguide_open_source_v2.0\build_10.7\mgdev\server\src\common\manager\FdoConnectionManager.cpp - MgFeatureServiceHandler.ProcessOperation line 83 file d:\buildforgeprojects\mapguide_open_source_v2.0\build_10.7\mgdev\server\src\services\feature\FeatureServiceHandler.cpp - MgOpGetClassDefinition.Execute line 157 file d:\buildforgeprojects\mapguide_open_source_v2.0\build_10.7\mgdev\server\src\services\feature\OpGetClassDefinition.cpp - MgServerDescribeSchema.GetClassDefinition line 1443 file d:\buildforgeprojects\mapguide_open_source_v2.0\build_10.7\mgdev\server\src\services\feature\ServerDescribeSchema.cpp - MgServerDescribeSchema.DescribeSchema line 538 file d:\buildforgeprojects\mapguide_open_source_v2.0\build_10.7\mgdev\server\src\services\feature\ServerDescribeSchema.cpp - MgServerDescribeSchema.ExecuteDescribeSchema line 171 file d:\buildforgeprojects\mapguide_open_source_v2.0\build_10.7\mgdev\server\src\services\feature\ServerDescribeSchema.cpp - MgFdoConnectionManager.Open line 862 file d:\buildforgeprojects\mapguide_open_source_v2.0\build_10.7\mgdev\server\src\common\manager\FdoConnectionManager.cpp
The short answer is:
- At least one of the layers was broken because it was linked to a database that didn't exist on our test machine. The old AJAX viewer would've gracefully handled it by simply not rendering that particular layer.
- The json output above is missing two } characters 1 - At the end of the error property of the json object 2 - At the end of the json object.
Could the MapGuide stack trace be interfering with the JSON output?
Change History (4)
comment:1 by , 17 years ago
Keywords: | fusion added |
---|
comment:2 by , 17 years ago
Milestone: | → 2.0 |
---|
comment:3 by , 17 years ago
Cc: | added |
---|---|
Owner: | set to |
comment:4 by , 17 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Doesn't happen now in RC4, using same dataset with same broken layer.
Paul, Should MGOS format the response in a certain way? Tom