Closed moihn closed 3 years ago
I really appreciate the contribution @moihn, Thank you 🙌 .
Did you test this PR with your WSDL and it worked fine? is this backwards compatible?
Yes, it works so far so good with our SOAP services. I think it is backward compatible for fields with nillable="false". But where nillable="true", I am not sure it is intended to be backward compatible, as this was zero initialized by Go in current master branch, and is never a nil value, so there is kind of semantics difference. Let me know if you have any concern.
Hi guys, it seems that multiple tests fail since that PR was merged.
Ex:
genTypes error template: types:43:59: executing "Attributes" at <.Nillable>: can't evaluate field Nillable in type *gowsdl.XSDAttribute
Thanks!
I will try to take a look this weekend.
New PR fixing the issue is created here : https://github.com/hooklift/gowsdl/pull/194
Hi,
Thanks for this gowsdl project, it helped a lot in our project. This is our 2 cents in supporting nillable=true attribute of WSDL, so that nillable fields can be identified in SOAP request and response, especially for fields of integer data types(int, int32, etc...).
We tried to read the gowsdl code generator design, and if we misunderstood anything, please don't hesitate to let us know, and we can update our code to make them right.
Thanks and regards