Hi Dave,
I've had a lot of trouble with generateDS not creating valid XML for the
XSDs I use. The biggest problem I had was getting generateDS to create XML
with valid namespaces. After looking at the code and running the debugger,
I believe the problem stems from the fact that generateDS creates a single
root with all the included/imported XSDs appended to it. This is done in
process_includes.prep_schema_doc().
After many tests I decided the best way to fix this was to avoid this
altogether and process each imported XSD independently. As a result of this
change it appeared necessary to have generateDS create a python module for
each XSD (or at least it was easier to do this). Having one python module
per XSD is better for me anyways as this is how we do it for our java code.
I now have a working version of this that works with the 100 or so XSD
files I use. I attempted to make this change without disrupting how
genereateDS works otherwise. In a previous email you mentioned there are
unit tests. Would you explain how to run these? Once I get those to pass
I'll check these in to my repo and submit a pull request.
Thanks,
George
------------------------------------------------------------------------------
LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99!
1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint
2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes
Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/22/13.
http://pubads.g.doubleclick.net/gampad/clk?id=64545871&iu=/4140/ostg.clktrk
_______________________________________________
generateds-users mailing list
generateds-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/generateds-users
