[mapguide-trac] #211: Serializing class definition to XML needs to be optimized

[MapGuide Open Source]

#211: Serializing class definition to XML needs to be optimized
-----------------------------+----------------------------------------------
 Reporter:  ronnielouie      |         Owner:       
     Type:  defect           |        Status:  new  
 Priority:  medium           |     Milestone:  1.3  
Component:  Feature Service  |       Version:  1.2.0
 Severity:  major            |    Resolution:       
 Keywords:                   |   External_id:       
-----------------------------+----------------------------------------------
Comment (by ronnielouie):

 It is rather cumbersome to get the original schema, remove the class, add
 to a temporary schema, serialize, remove from temporary schema, add back
 to original schema.

 It seems the reason behind this is that a class can have only one parent
 object (schema) at a time.  Because the class is moved to a temporary
 schema for serialization, it must be removed from the original parent
 schema before it can be added to the temporary one.  Same goes for when it
 is returned back to the original.

 A better approach would be to clone the feature class, then the clone can
 be manipulated (added to the temp schema, for writing out to xml) without
 touching the original schema.

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