Opened 14 years ago

Closed 13 years ago

#1700 closed defect (fixed)

Error editing some existing ODBC feature sources

Reported by: andrewd Owned by: jng
Priority: medium Milestone: Maestro-3.5
Component: Maestro Version: 2.1.0
Severity: major Keywords:
Cc: External ID:

Description

When I try to edit the schema of a particular ODBC feature source, I get an error in Maestro 3.1. I can edit the same feature source using 2.1.4.5245 without problems. Other ODBC feature sources seem to work fine. Oddly enough, if I create a new feature source and point to the same problem dsn, I can successfully edit the schema.

Here's the XML for the feature source (it's got a config file, but I'm not sure how to get at that in 3.1). Attached is a screen cap of the error.

<?xml version="1.0" encoding="utf-8"?> <FeatureSource xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xsi:noNamespaceSchemaLocation="FeatureSource-1.0.0.xsd">

<Provider>OSGeo.ODBC</Provider> <Parameter>

<Name>DataSourceName</Name> <Value>petitcodiac_sections</Value>

</Parameter> <Parameter>

<Name>GenerateDefaultGeometryProperty</Name> <Value>false</Value>

</Parameter> <ConfigurationDocument>config</ConfigurationDocument>

</FeatureSource>

Attachments (2)

Capture.PNG (80.6 KB ) - added by andrewd 14 years ago.
screen cap of "edit schema" error
config.txt (25.9 KB ) - added by andrewd 14 years ago.
config xml

Download all attachments as: .zip

Change History (7)

by andrewd, 14 years ago

Attachment: Capture.PNG added

screen cap of "edit schema" error

comment:1 by jng, 14 years ago

You can get at the raw XML configuration document at the bottom of the Feature Source editor. If you can attach a file containing said XML content, that would be very helpful

by andrewd, 14 years ago

Attachment: config.txt added

config xml

comment:2 by jng, 14 years ago

I see what's wrong. My XML configuration document classes are too strict with reading unqualified element names (it's always expecting the fdo: qualifier).

I'll relax this requirement

comment:3 by jng, 14 years ago

Just to clarify, the requirement will be relaxed for reading

When writing the fdo: qualifier for element names and attributes will still be used where necessary

comment:4 by jng, 14 years ago

Milestone: Maestro-3.1Maestro-3.5

comment:5 by jng, 13 years ago

Resolution: fixed
Status: newclosed

Fixed with revisions r6255 and r6282

Note: See TracTickets for help on using tickets.