Maestro - LayerDefinition Does Not Show 'Dirty' or Invalid When Opened and Feature Class Unavailable

[crispinatime]

Take the following scenario:

1) Create a feature source - e.g. to a SHP folder with lots of feature classes

2) Create a layer to a feature class

3) Stop services / remove class / restart services

4) Open the layer definition and click save

Even with "Validate on Save" option set, there is no warning on either the opening or saving despite an invalid feature class.

[crispinatime]

Save (with Validation enabled) now flags this up.

Ideally this could also be raised as a warning when opening.

A similar issue occurs when the Geometry Property is changed. We recently had an issue and tried to track-down by opening a Session: layer in Maestro. All looked OK as the Geometry drop-down was populated. Only when viewing the XML did we see that there was an invalid property name in the geometry property - but the UI view in Maestro showed the valid value. This scenario can be tested by:

1) Turn OFF Maestro validation on save

2) Open a valid .LayerDefinition in XML and edit the geometry property to an invalid name

3) Save and close

4) Turn ON Maestro validation

5) Open the .LayerDefinition and the full UI - the invalid name shows up and no warning or dirty state

6) The Save button can be clicked and there is no Validation warning implying to the user that the Layer is valid. You need to edit another field to force-dirty before the validation happens.

[jng]

r8087 will now flag any bad Feature Source, Feature Class or Geometry fields when you open a Layer Definition