You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
RFC 5730 is heavily dependent on namespaces to perform the proper action over the EPP protocol. Sadly, the Go XML standardlibrary has a lot of known issues.
Some people have tried to work around this but I still haven't found a proper solution. Since I want to implement all the types required for EPP both as a server and a client I need to be able to both marshal and unmarshal the data.
A combination of multiple/wrapped types and go-xml enables me to at least do the marshalling (without proper NS registration though). By wrapping yet another type I can also unmarshal.
dim:=DomainInfoMarshal{
Info: DomainInfo{
Name: "example.se",
},
}
b, _:=xml.Marshal(dim)
p, _:=xmltree.Parse(b)
// Traverse P and look for p.Name.Space. If set, create an xmlns:alias and use// on children by setting child.Name.Local to alias:name
This does not feel like an optimal solution.
The text was updated successfully, but these errors were encountered:
RFC 5730 is heavily dependent on namespaces to perform the proper action over the EPP protocol. Sadly, the Go XML standardlibrary has a lot of known issues.
Some people have tried to work around this but I still haven't found a proper solution. Since I want to implement all the types required for EPP both as a server and a client I need to be able to both marshal and unmarshal the data.
A combination of multiple/wrapped types and go-xml enables me to at least do the marshalling (without proper NS registration though). By wrapping yet another type I can also unmarshal.
Example
Incomming data to be unmarshalled, independent of namespace:
And to generate a domain info request:
This does not feel like an optimal solution.
The text was updated successfully, but these errors were encountered: