On Tuesday, 7 May 2019 07:19:25 EEST Dave Kuhlman wrote: > I think you are likely right to focus on that xs:any definition > inside the CustomContent. Normally, the code generated by > generateds has to know what kind of object it is supposed to build > at any given point in the object tree, and when it does, it builds > an instance of a generated Python class. Using xs:any effectively > says: "I don't know which kind of object to build. > > I'll look into it. > Unfortunately, tomorrow I take off for a week of travel any > vacation. So, it might be a few days before I work on this. > > If you learn anything more, please pass it along. And, I'll do the > same.
see my comments https://stackoverflow.com/questions/56005920/generateds-stops-processing-child-elements GDS is well aware of any-beast, it just skips it without creating class- mappings. I'm just not sure where/how there is a definitions for - basic xml-schema types (xs:string, xs:boolean etc) versus - parsed schema structure I guess it's in the generateDS.py code, in sax-handler? Giving a name and type for each element obviously makes a difference too. Much easier digging into this kind of project if one has himself gradually written the whole code, hopping into end result is somewhat difficult. Juha -- t...@iki.ee | http://tuju.ee | sip:t...@iki.ee | +3726311345 | +3725025337 Better to have one, and not need it, than to need one and not have it. _______________________________________________ generateds-users mailing list generateds-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/generateds-users
