Comments (3)
Hi guys, I'm facing that kind of issue too.
You need to adapt the SOAP structs to your needs in soap.go, which means forking this repo with your modifications, not an ideal situation.
For example, your SOAPEnvelope struct should be something like that, notice the soapenv in the xml struct tag :
type SOAPEnvelope struct {
XMLName xml.Name `xml:"soapenv:Envelope"`
XmlNS string `xml:"xmlns:soapenv,attr"`
XmlCustomNS string `xml:"xmlns:end,attr"`
Header *SOAPHeader
Body SOAPBody
}
type SOAPHeader struct {
XMLName xml.Name `xml:"soapenv:Header"`
Headers []interface{}
}
type SOAPBody struct {
XMLName xml.Name `xml:"soapenv:Body"`
...
}
You will need to set your XmlCustomNS in the SOAPEnv instance :
Line 418 in 0f6b60e
envelope := SOAPEnvelope {
XmlNS: XmlNsSoapEnv,
XmlCustomNS: "http://enduser.service.web.vcp.netcup.de/",
}
I'm kinda thinking it could be a good use of the new golang generics : define your types and pass them at runtime to the soap Client... keep an eye on my fork, if I get around to implement that.
For <end:getVServers>
unfortunately, this "end" prefix depends on the templates used to generate the go code and I'm still wondering how to change that.
If you look at :
Line 206 in 0f6b60e
That's where the
"xmlns="url..."
comes from, but we want a prefix to the xml tag name instead.from gowsdl.
+1
from gowsdl.
+1
from gowsdl.
Related Issues (20)
- Namespace support: naming collisions / redeclared types in different namespaces HOT 1
- XML name field tag conflicts with struct's XMLName field
- dump request
- Error when parsing response: Expected param start-info="application/soap+xml", got text/xml HOT 2
- Incorrect namespace handling HOT 5
- Empty strings in enums results in broken code HOT 1
- nodes with multiple namespace are not resolved by the generated code
- Some complex types are missing the namespace
- Separation of generated code into packages HOT 2
- 1511:11: expected type, found '-' (and 3 more errors) HOT 2
- Cut a new Release v0.6.0 HOT 1
- Failing test TestEPCISWSDL HOT 1
- gowsdl does not respect the targetNamespace value on wsdl definition.
- SOAP Header element not present
- generate code from wsdl HOT 1
- date format: cannot unmarshal into soap.XSDDate
- Any plan to update the go.mod with latest versions. Seeing some vulnerabilities reported with the current versions used
- bad type generation for xs:choice + maxOccurs="unbounded"
- Conflicting XML tags are generated, if a struct with field XMLName is used inside another struct
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from gowsdl.