>    Hi Dave,
> 
>    I just tested your new patch. Yes, the *Section elements are generated!
> 
>    cid:image004.jpg@01CF3BA0.FEB8E510
> 
>    But seems not all elements are generated properly. Showed as below, sub
>    elements under Children/VM/VCloudExtension are not generated properly.
> 
>        <Children>
> 

Jinquan,

The file 1.xml does not seem to match well against the schema.  See
my comments on testing with 2.xml, below.

Also, when I use a generated module to parse and export 1.xml, I
see that the specific elements LeaseSettingsSection,
StartupSection, NetworkSection, etc are all exported with the
generic name Section.  I'm working on that.

[snip]

> 
> 
> 
>    I also tested another vcloud xml below and found the yellow highlighted
>    part is not generated. Seems HardwareCustomizationType is missing  in
>    generated py file.

You are correct.  HardwareCustomization element is missing from the
exported output.  I went looking for a definition of that element.
But the definition of SourcedVmInstantiationParams does not seem to
contain HardwareCustomization.  So, I tried to validate 2.xml
against the vcloud.xsd schema.  Here is what I got:

    $ xmllint --noout --schema Vcloud_schema/1.5/schemas/vcloud/vcloud.xsd 2.xml
    2.xml:37: element HardwareCustomization: Schemas validity error :
    Element '{http://www.vmware.com/vcloud/v1.5}HardwareCustomization':
    This element is not expected. Expected is (
    {http://www.vmware.com/vcloud/v1.5}LocalityParams ).
    2.xml fails to validate

I also tried to validate 2.xml against vmwextensions.xsd, because I
am not sure which schema 2.xml is an instance of:

    xmllint --noout --schema 
Vcloud_schema/1.5/schemas/extension/vmwextensions.xsd 2.xml
    2.xml:37: element HardwareCustomization: Schemas validity error :
    Element '{http://www.vmware.com/vcloud/v1.5}HardwareCustomization':
    This element is not expected. Expected is (
    {http://www.vmware.com/vcloud/v1.5}LocalityParams ).
    2.xml fails to validate

If the schema does not specify that subelement, then a module
generated by generateDS.py from that schema will not contain code to
parse of export that sub-element.

Can you suggest some reason why the HardwareCustomization element is in
2.xml, or why it is not specified in the schema?

Dave

-- 

Dave Kuhlman
http://www.davekuhlman.org

------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
_______________________________________________
generateds-users mailing list
generateds-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/generateds-users

Reply via email to