loopbackio / loopbackio/strong-soap
incorrect packet generated
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 410
- Forks
- 162
- Avg merge
- 4h 36m
- Merged PRs (30d)
- 7
Description
i am facing issue with strong soap 4.1.8. it is not generating soap request as accepted by server.
working soap request:
```
```
code generated soap request:
```
1.0
```
i tried
```
wsdl_options: {
overrideRootElement: {
namespace: 'http://schemas.xmlsoap.org/soap/envelope/',
xmlnsAttributes: [
{ name: 'xmlns:soapenv', value: 'http://schemas.xmlsoap.org/soap/envelope/' },
{ name: 'xmlns:api', value: 'http:///cpsinterface/api_requestmgr' },
{ name: 'xmlns:req', value: 'http://cpsinterface/request' },
{ name: 'xmlns:cus', value: 'http:///cpsinterface/customizedrequest' },
],
},
useEmptyTag: false,
preserveWhitespace: true,
},
SOAPAction: '"http:///cpsinterface/api_requestmgr/APIRequest"', // SOAPAction for the operation
httpHeaders: {
'Content-Type': 'text/xml; charset=utf-8', // SOAP 1.1 Content-Type
}
client.addSoapHeader('
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 by reproducing the SOAP request generated by strong-soap 4.1.8 from the issue's example and compare its namespaces and structure with the accepted request. Investigate the shown wsdl_options overrideRootElement, SOAPAction, and addSoapHeader configuration. Done means identifying and documenting a reproducible correction that produces the server-accepted XML.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100