-
Notifications
You must be signed in to change notification settings - Fork 375
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
Double definition in WSDL when collection of enums is named with XmlElement #1070
Comments
This issue is stale because it has been open for 30 days with no activity. |
No response after five weeks. Would just like to know if I am doing something wrong, or there is a bug in SoapCore, both for this issue and for #1069. |
No wonder there are only a few open issues for this project. They get automatically closed after two months. Lack of response is concerning. To say "won't do, don't have time right now" would be at least understandable. One star. |
I seem to be the only somewhat active maintainer here and I don't have a lot of time to dedicate to this project. You seem to have encountered a bug. A PR would be appreciated if you can find the time. |
This issue is stale because it has been open for 30 days with no activity. |
This issue was closed because it has been inactive for 14 days since being marked as stale. |
If a collection of enums has a bare
XmlElement
attribute attached then WSDL is correct, but if the name is added to the attribute then weird double definition appears in WSDL. Take this code:Resulting WSDL will have this:
This
simpleType
is expected, but thiscomplexType
is an error. The error will not show ifXmlElement
attribute does not have theElementName
set.The text was updated successfully, but these errors were encountered: