-
Notifications
You must be signed in to change notification settings - Fork 158
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Header does not use required prefix #323
Comments
This comment was marked as spam.
This comment was marked as spam.
If I may join this party late, @saristar does your WSDL define your header? I can see the module has a unit test ('should add soap headers' in client-test.js) just for this case, and it passes -- unless I change qname and/or the header's name, in which case the output header element lacks the given qname. You can also see this header defined in the WSDL imported by the unit test, and the unit test's comments indicate it wants the "header schema defined in default-namespace.wsdl". Therefore I ask whether your WSDL defines the header you want; seems like the output doesn't respect otherwise. For now I worked around it by passing the header as string literal XML. As you saw, you can also still the header as object, but you lose the qname. I'm not sure what it('should add soap headers with a namespace') is for, since it doesn't seem to test for a namespace in the header. |
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.
I want the header to generate with
oe
prefixThis is how it is built from strong-soap
Expected Output:
I want the header to be built this way.
The text was updated successfully, but these errors were encountered: