-
Notifications
You must be signed in to change notification settings - Fork 616
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
namespacing issue #820
Comments
Any updates on this? Have the same issue |
I'm don't have any new information on this issue. I did find that you can manually add the namespace to the client call like this:
When you are creating the client you need |
Found a way around this by writing raw xml and adding namespaces manually. |
Having the same issue here
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue is now closed due to inactivity. If you believe this needs further action, please re-open to discuss. |
I have an issue that I believe is in regards to namespaces. The WSDL is attached or can be downloaded from here: http://promostandards.org/content/wsdl/Order%20Shipment%20NotificationService/1.0.0/OSN-1-0-0.zip
When the request is generated it looks like this:
This results in a soap fault.
When SoapUI constructs the request using the same WSDL it looks like this
You can see that SoapUI has placed the username and password inside the "shar" namespace. I noticed that this is not directly listed in the WSDL or in any XSD file directly loaded by the WSDL. It gets loaded something like WSDL => XSD file => XSD file containing shar namespace. could that be the issue? How can I add the namespace to just 3 of the keys? I'm using savon 2.11.1 and nori 2.6.0
WSDL:
OSN-1-0-0.zip
The text was updated successfully, but these errors were encountered: