#165 closed defect (fixed)
Missing VectorScaleRange in LayerDefinition causes Runtime Exception
Reported by: | zspitzer | Owned by: | waltweltonlair |
---|---|---|---|
Priority: | medium | Milestone: | 2.1 |
Component: | Mapping Service | Version: | 2.0.0 |
Severity: | major | Keywords: | |
Cc: | External ID: | 939557 |
Description
for example not having <VectorScaleRange>.....</VectorScaleRange> in a layer definition for example throws
An exception occurred in DB XML component. Error: XML Indexer: Parse error in document at line, 9, char 28. Parser message: Not enough elements to match content model : '(ResourceId,Opacity,(FeatureName,FeatureNameType,Filter,PropertyMapping,Geometry,Url,ToolTip,VectorScaleRange),ExtendedData1)'
however having an empty <VectorScaleRange></VectorScaleRange> ie no styling or scale ranges
will case a runtime error and a console dialog on xp.
the following is listed in the logs
- MgStylizationUtil.StylizeLayers line 923 file c:\build_bond_area\mapguide_open_source_v1.2\build_13.7\mgdev\server\src\services\mapping\StylizationUtil.cpp Failed to stylize layer: Datasets_ABORIG_NT
Change History (8)
comment:1 by , 18 years ago
comment:2 by , 18 years ago
Yep, having an empty VectorScaleRange is allowed, according to the schema. The server needs to gracefully handle this case.
comment:3 by , 17 years ago
External ID: | → 939557 |
---|
comment:4 by , 17 years ago
Milestone: | 1.2 → 1.3 |
---|
comment:5 by , 17 years ago
Milestone: | 2.0 |
---|
comment:6 by , 17 years ago
Owner: | set to |
---|
comment:7 by , 17 years ago
Milestone: | → 2.1 |
---|---|
Resolution: | → fixed |
Status: | new → closed |
Version: | 1.2.0 → 2.0.0 |
This was fixed at some point in the 2.0 code stream.
comment:8 by , 17 years ago
I encountered no problems when testing with a layer definition with an empty VectorScaleRange element.
I am using the java api on xp btw