Closed gokulvenkats closed 4 years ago
I can imagine this might happen if you generate bindings for multiple schema in separate calls to pyxbgen
. You might need to do something like this.
I can imagine this might happen if you generate bindings for multiple schema in separate calls to
pyxbgen
. You might need to do something like this.
Hi,
Still I face the same issue, copied the complete error below:
$ /opt/pypy3-v6.0.0/bin/pypy3 /opt/pypy3-v6.0.0/bin/pyxbgen --version pyxbgen from PyXB 1.2.5
$ /opt/pypy3-v6.0.0/bin/pypy3 /opt/pypy3-v6.0.0/bin/pyxbgen \
--schema-location=/tmp/CPRulesOrderSchema.xsd --module=cporder \ --schema-location=/tmp/CPRulesResultSchema.xsd --module=cporder.result \ --module-prefix=lexisnexis \ --archive-to-file=lexisnexis/lexisnexis.core.wxs
Traceback (most recent call last):
File "/opt/pypy3-v6.0.0/bin/pyxbgen", line 52, in
I would need to see the schema to figure out what's going on. However, I see you're using PyXB 1.2.5. Please update to the latest release (1.2.6) first to see whether this problem has been solved.
pyxb.exceptions_.NamespaceUniquenessError: http://cp.com/rules/client: name national_credit_file used for multiple values in elementDeclaration
I even tried archive-path and archive-to-file but it is not working for NamespaceUniquenessError in elementDeclaration.
Is NamespaceUniquenessError for elementDeclaration and typeBinding different?