Maestro - Schema Versions and Updates

[crispinatime]

When I create a new layer at a version below my current server version (eg 2.3 on a MapGuide 2.4 server) the "Upgrade" your schema button works. However, for watermarks this "Upgrade" button fails.

Though MG 2.4 is only in RC it would be nice to see it in the resource list and update a Maestro that is aware of the current build number so that we can test both in parallel.

An explanation as to what the meaning of a v2.4 Watermark for example would also be handy. There is obviously a OSGeo.MapGuide.ObjectModels.WatermarkDefinition-2.4.0.dll file - but the \Schemas folders only includes a 2.3 version so what does an upgrade actually mean?

[crispinatime]

Watermark Upgrade Exception Err (does not occur AFTER initial save)

[jng]

Could you attach a copy of the v2.3 Watermark that fails to upgrade?

[crispinatime]

It's only an unsaved one that fails.

It's more due to the fact that a new/blank v2.3 watermark will not *immediately* save without error (can you replicate that?). You need to change the type to "image" and upload an image or work out which are the mandatory elements required for "text" ... so it's actually more about default usability than upgradeability.

Having found both a "WatermarkDefinition-2.3.0.xsd" and a "WatermarkDefinition-2.4.0.xsd" under \Maestro\OSGeo.MapGuide.MaestroAPI\Schemas both appear identical apart from that the 2.3 has:

<xs:include schemaLocation="SymbolDefinition-1.1.0.xsd"/>

and the 2.4 has:

<xs:include schemaLocation="SymbolDefinition-2.4.0.xsd"/>

But only the 2.3 is copied to the \out\[BUILD]\Schemas folder? So I still don't see the difference or need but I may be missing something!

[jng]

Maestro only uses the xsd files for local validation of XML content and does not play any part in the current issue at hand.

Anyway, I can reproduce the problem at hand

[jng]

Fixed in trunk (r6812) and 4.0.x branch (r6813)

Problem was due to insufficient default values for a new Simple Symbol Definition that satisfies the minimum content model requirements. For a text-based Simple Symbol Definition, this requires the textual content (empty string will suffice) and font name elements be specified.