Opened 11 years ago

Closed 11 years ago

Last modified 11 years ago

#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

Change History (8)

comment:1 Changed 11 years ago by zspitzer

I am using the java api on xp btw

comment:2 Changed 11 years ago by waltweltonlair

Yep, having an empty VectorScaleRange? is allowed, according to the schema. The server needs to gracefully handle this case.

comment:3 Changed 11 years ago by rexszeto

External ID: 939557

comment:4 Changed 11 years ago by tomfukushima

Milestone: 1.21.3

comment:5 Changed 11 years ago by tomfukushima

Milestone: 2.0

comment:6 Changed 11 years ago by waltweltonlair

Owner: set to waltweltonlair

comment:7 Changed 11 years ago by waltweltonlair

Milestone: 2.1
Resolution: fixed
Status: newclosed
Version: 1.2.02.0.0

This was fixed at some point in the 2.0 code stream.

comment:8 Changed 11 years ago by waltweltonlair

I encountered no problems when testing with a layer definition with an empty VectorScaleRange element.

Note: See TracTickets for help on using tickets.