loopbackio / loopbackio/strong-soap
Header does not use required prefix
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 410
- Forks
- 162
- Avg merge
- 4h 36m
- Merged PRs (30d)
- 7
Description
I'm trying to add header using client.addSoapHeader() method. The problem with the method is it is not using the required prefix in the xml output.
This is how I'm building the header.
```
const soaH = {
"SOAHeader": {
"Responsibility": "MANAGER",
"RespApplication": "AR",
"SecurityGroup": "STANDARD",
"NLSLanguage": "AMERICAN",
"Org_Id": "1"
}
}
const qname = new QName('{http://xmlns.oracle.com/apps/ont/soaprovider/plsql/oe_inbound_int/}oe:SOAHeader')
client.addSoapHeader(soaH, qname)
```
I want the header to generate with `oe` prefix
This is how it is built from strong-soap
```
*********
*********
MANAGER
AR
STANDARD
AMERICAN
1
1.0
5112
```
Expected Output:
```
*********
*********
2020-10-06T05:51:58.527Z
MANAGER
AR
STANDARD
AMERICAN
1
1.0
5005
```
I want the header to be built this way.
```
MANAGER
AR
STANDARD
AMERICAN
1
```
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 tracing client.addSoapHeader and the QName handling used to serialize the supplied header. The payload names no source files or tests, so locate the serializer entry point and existing SOAP-header coverage first; done means the generated header uses the requested oe prefix for SOAHeader and its child elements.
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
- Mostly clear
- Newbie friendliness
- 35/100