David A. Arroyo

Your idea about calling the unmarshaller is interesting. I don't think it's what you meant, but what if, for any types that have default attributes, we construct an xml document...

Using pointers for all struct fields is the easiest way, I think. @homanchou , I've just pushed the branch `omitempty-structs` which makes this change. Can you give it a try...

@homanchou , have you been able to try the changes made in the `omitempty-structs` branch? If not, could you share the XSD and sample data you used, so I can...

There has been some movement on https://github.com/golang/go/issues/11939 which would resolve our problem. That said, that issue has been open for 3 years, and I don't think everyone will adopt Go...

the omitempty-structs branch implements solution 1, using pointers for all fields. this seems to work well for those who have used it, so i'm thinking we can move it into...

I've reverted. I think I can see the error here: https://github.com/elliots/go-xml/blob/2161665b1a098d50c305f0bf938f7aca2e05fee0/xsdgen/xsdgen.go#L697 I don't think that's the right way to construct a pointer using go/ast. I haven't tried yet but it...

I started work on the `multiref` branch, but unfortunately I am not close to resolving this issue, and will have limited time to make progress for the next month or...

The error is here (note the extra space) type struct { Type Anon52 `xml:"type,attr"` } It seems similar to #99 . It appears to be trying to generate a complexType...

This is probably a duplicate of #86 . Most likely one of those schema contain a recursive type definition, and xsdgen chokes on that.

I really like the fact that generated code uses basic types like `time.Time` and `[]byte` (for `base64Binary`) rather than exporting custom types, and would like to keep that property, if...