-
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
namespace mismatch #942
Comments
👋
By travelling backwards in versions used, perhaps you can find a point in time where things didn't break? |
wasabi outputs:
which to me looks like wasabi probably does the correct thing but the actual call is wrong. Same result if I go back to e.g. (and the allowed minor combinations in between) I wonder if savon is either overwriting ns3, or then just picking the namespace to use from targetNamespace instead of from the operation? |
So as a workaround i can specify a global |
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. |
I have the same issue. Even reverting to older versions of savon and/or wasabi doesn't help. Starting from version 2.8.0 savon at least uses the correct namespace id, in my case going from xmlns:ws to xmlns:ccma3. However it uses the wrong value for that namespace. It seems to use the targetNamespace from the wsdl. |
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. |
Bug report
Given the following WSDL
AFO.wsdl.zip
and the following test code:
Produces the following request:
In the WSDL:
xmlns:ns3="http://your.company.net/AFO/LstSINDIV"
in the request:
xmlns:ns3="http://your.company.net/AFO"
Current behavior:
Steps to reproduce current behavior:
Expected behavior:
The operation should be called with the correct namespace
System information:
The text was updated successfully, but these errors were encountered: