loopbackio / loopbackio/strong-soap
"Cannot parse response" While calling method on WSDL
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 410
- Forks
- 162
- Avg merge
- 4h 36m
- Merged PRs (30d)
- 7
Description
i got error when i try to change my SOAP url to static file, previously when i use the url its work properly the url its manage by outsource, i download the result from that URL and try to connect by local file, here the code
soap.createClient(path.join(__dirname, '../wsdl/wsdl.xml'), {}, (err, client) => {
if (err) return reject(err);
client.setSecurity(new soap.BasicAuthSecurity(config().username, config().password));
const method = client.agentActivation;
console.log(method, 'method');
method(args, (err, result, envelope, soapHeader) => {
if (err) {
logger.info('error method');
logger.info(err.message);
return reject(err);
}
logger.info(result);
return resolve(result);
});
});
i got the method from client but when i call the method i got error "Cannot parse response "
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the client creation using wsdl/wsdl.xml and the client.agentActivation call shown in the issue. Compare how the local WSDL and the outsourced URL are handled, then reproduce the "Cannot parse response" callback error; done means the static WSDL request parses and returns a result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100