[Mapguide-trac] [mapguide-trac] #2424: Maestro - LayerDefinition Inefficiencies with Large Schemas

[MapGuide Open Source]

#2424: Maestro - LayerDefinition Inefficiencies with Large Schemas
----------------------------+-----------------------------------------------
   Reporter:  crispinatime  |       Owner:       
       Type:  defect        |      Status:  new  
   Priority:  low           |   Milestone:       
  Component:  General       |     Version:  2.5.0
   Severity:  trivial       |    Keywords:       
External_id:                |  
----------------------------+-----------------------------------------------

Comment(by jng):

 Ok after a review of the validation code. I've come to the conclusion that
 the identity property check when validating a Feature Source is really a
 superfluous validation check that doesn't have to be done (it only
 triggers an informational result, and not a warning or error).

 It's only an issue when a referencing layer is added to a Map Definition
 and is marked as selectable. Such cases are now being checked at the Map
 Definition validation level as of r8029.

 But more importantly, when saving a Layer Definition it should only be
 doing a shallow validation of the Layer Definition itself and not any
 upstream dependent resources. This was fixed in r8028

 So I've decided to remove this identity property check from the Feature
 Source validator for r8030.

 If these 3 changes as a whole solves your issue, I guess you can close
 this ticket without having to wait for the release of 2.6 beta 1.

-- 
Ticket URL: <http://trac.osgeo.org/mapguide/ticket/2424#comment:6>
MapGuide Open Source <http://mapguide.osgeo.org/>
MapGuide Open Source Internals