loopbackio / loopbackio/strong-soap
Modifiy XML and replace ns1: by sil:
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 410
- Forks
- 162
- Avg merge
- 4h 36m
- Merged PRs (30d)
- 7
Description
# Description/Steps to reproduce
```
var url = "https://www.xxx.fr/xxxxx/sws/sws.asmx?wsdl";
var args = {
"SWSLogin": "xxxxx",
"SWSPassword": "xxxxx",
"USRLogin": "xxxxx",
"USRPassword": "xxxxx"
};
soap.createClient(url, wsdlOptions, function(err, client) {
var method = client['SWS_SiteLogin'];
console.log(method);
method(args, function(err, result, envelope, soapHeader) {
//response envelope
console.log('Response Envelope: \n' + envelope);
//'result' is the response body
console.log('Result: \n' + JSON.stringify(result));
});
console.log(client.lastRequest);
});
```
# Request
```
xxxxxx
xxxxxx
xxxxxx
xxxxxx
```
# Expected request
```
xxxxxx
xxxxxx
xxxxxx
xxxxxx
```
# Additional information
can you please help me to find the way to change xml and replace ns1 by sil ?
Best regards
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 createClient and the request output exposed through client.lastRequest, using the supplied SOAP request and expected request as the comparison. Trace how the operation namespace prefix is selected; done means the generated request uses sil for the service elements while retaining the soap envelope prefix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100