-
Notifications
You must be signed in to change notification settings - Fork 382
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
Element type renaming #24
Comments
@notzippy the generator is assigning whatever is being declared in the WSDL. If the type is named |
maybe we should use whatever is coming in the |
ah nevermind, it has the same name as the type. Yeah, it is just generating whatever the WSDL has. |
@notzippy gowsdl does not yet support namespaces, mainly due to Go's lack of proper support in the standard library. |
This isnt a namespace issue, it is the |
I will start off with I am no wsdl expert - given the following wsdl fragment
The proper output response is
What is being generated is
Notice the
ValidateCityPostalCodeZipRequestContainer
vsValidateCityPostalCodeZipRequest
The later is correct, I assume this is described in<xsd:element name="ValidateCityPostalCodeZipRequest" nillable="true" type="tns:ValidateCityPostalCodeZipRequestContainer"/>
The structure is good, just the xml.Name should be changed
XMLName xml.Name
xml:"http://purolator.com/pws/service/v1 ValidateCityPostalCodeZipRequest"``The text was updated successfully, but these errors were encountered: