You've specified that all three schema are in the same namespace: are you
declaring that namespace in each, or are you using a chameleon schema model
where A.xsd has no namespace, and consequently gets assigned one by the fact
of its inclusion into B and C? What bothers you about using a gathering
Yes, I have thought about this solution but it would be my "backup"
solution.
In C++, CodeSynthesis XSD creates a header file A.hpp containing the types
defined in A.xsd. This header file is then included in the other header
files (B.hpp, C.hpp). There is no problem like described before since the
The best way to deal with this is to create a single schema that just
includes both B.xsd and C.xsd, and generate the bindings using it. A.xsd
will come along for the ride. Since B and C represent objects in the same
namespace, they really need to be generated into a single Python module, and
PyX
