Fix complex content array restriction type #105
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello,
I was using your library with a WSDL using array contentType restrictions, and I noticed the generated code had errors in it. The errors were all about the same thing :
Originally generated code, with the error :
As you may have noticed, the
Invoiceitem
struct has been generated with the correct name, but the type referenced inInvoiceitemArray
lacks the capitalisation. While with another WSDL, the naming was right, but it used a different way to declare its arrays.Also, by using this fix, we get arrays of primitive types and not arrays of pointers to primitive types, which is, performance wise, a good thing. (while still getting pointers to composite types)
Source WSDL : https://sr-pp.swissbilling.ch/EShopRequestV2Sec_DotNet.wsdl
The important extract of this WSDL:
I'm not really familiar with this code base, so please tell me if there's something wrong / I haven't seen.
Thank you, Benjamin.