Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

String and Byte[] are special-cases since they are built in types tha… #960

Conversation

andersjonsson
Copy link
Collaborator

@andersjonsson andersjonsson commented Sep 13, 2023

…t C# sees as enumerable. They should not be unbounded in the wsdl since that would cause clients to generate byte[] as byte[][] etc.

fixes #959

Also added support for ElementName-property of XmlElementAttribute. There are lots of scenarios around this attribute that are still not supported

andersjonsson and others added 6 commits September 13, 2023 10:48
…t C# sees as enumerable. They should not be unbounded in the wsdl since that would cause clients to generate byte[] as byte[][] etc.

fixes DigDes#959
…Name"-property of XmlElementAttribute was not used as name in the wsdl. Unclear if this change will cause havoc
@kotovaleksandr kotovaleksandr merged commit 1a3197d into DigDes:develop Sep 15, 2023
3 checks passed
vidrenning added a commit to vidrenning/SoapCore that referenced this pull request Jan 30, 2024
This is a regression of DigDes#960.
In commit 5026da3, the AddSchemaType()
method was changed to contain a special case for string and byte[].
However this breaks the situation where the inner type of a list is
string. In that case, maxOccurs must be set to "unbounded" for the
string element. So this commit reverts that change and instead fixes the
original issue at another place.

Fixes DigDes#988
@andersjonsson andersjonsson deleted the fix-wsdl-error-for-string-and-bytearray branch February 5, 2024 07:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Issue With Data Types when using XmlSerializer
2 participants