Comments (5)
Hey, did you ever figured this out? I'm stuck with the same problem. Not sure what I'm missing...
from soap.
Unfortunately not 😞
from soap.
I did. Turned out to be an inconsistent namespace definition in the WSDL I was targeting.
from soap.
I am struggling with this issue currently - trying to use this client with the Salesforce WSDL. I can provide more details (wsdl, request body being generated by soap, example of "correct" request body, etc. if anyone has interest and bandwidth to try and help.
from soap.
I've had issues with the namespace problem too - got it working by going over the lib's code and seeing that it's using some configurations (it helped initially):
config :soap, :globals,
env_namespace: "soapenv",
version: "1.1",
custom_namespaces: %{
aut: "some_action_url",
veh: "some_other_action_url"
}
Unfortunately, after a few days, the lib doesn't build the correct request again and i had to use a "hacky" way to do the requests:
- made a template of the body of the request
- sent the filled template with a "regular" HTTP client
- used
:sweet_xml
to handle the response (also this lib'sSoap.Response.parse/2
worked)
EDIT / UPDATE:
After digging around the lib, i found that my issue was that the wsdl
that i'm using doesn't have complex_types
filled (they're linked from another location, but the lib isn't able to / doesn't read them) - that data was needed for my problem (action-namespace mismatch) to be gone.
For my case, the solution was like this:
extra_complex_type = %{
name: "action_name",
type: "name_space:action_name"
}
wsdl = %{wsdl | complex_types: [extra_complex_type | wsdl.complex_types]}
from soap.
Related Issues (20)
- Support sweet_xml 0.7 HOT 3
- Invalid function spec for Soap.call
- SalesForce metadata WSDL parsed incorrectly HOT 1
- Library can not parse older formatted WSDL files HOT 1
- WSDL parse crashes HOT 1
- Operations not found in our WSDL HOT 5
- expected a map, got: nil with Soap.call HOT 21
- Issue parsing wsdl HOT 1
- Expose HTTPoison config HOT 2
- Are params currently supported? HOT 1
- Error (Protocol.UndefinedError) HOT 1
- Schema imports broken for url wsdl HOT 2
- Map into Map as params? HOT 3
- No error handling for parse_from_url
- The wsdl file does not get parsed HOT 1
- XSD file is not being parsed HOT 5
- (ArgumentError) could not fetch application environment :globals for application :soap because configuration :globals was not set HOT 5
- Type spec failures
- Add support for MTOM responses
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 soap.