I have been able to generate usable code both by using the
no_process_includes parameter and by raising the limit. My only concern is
to confirm that in both cases the generated code will behave in the same
way. I would also be interested to understand why the generated code is
different but that i
> From: Daniel Browne
>Sent: Monday, October 22, 2012 8:14 AM
>
> I've changed the hard coded limit mentioned previously to 1.
> Looking at the generated files, I have noticed that the hacked and
> normal files differ in the following way.
>
> In the xsd file, there a several sections structu
I've changed the hard coded limit mentioned previously to 1. Looking at
the generated files, I have noticed that the hacked and normal files differ
in the following way.
In the xsd file, there a several sections structured in the following
manner:
Atleast one element under searchCriteria
I'm using generateDS to process a large XSD file which does not have any
includes or imports in it. It does have what I understand to be anonymous
complex types (no "name" attribute). When I process the file normally I get
the following error:
# generateDS.py -o output.py -s outputsubs.py input.xs
