-
Notifications
You must be signed in to change notification settings - Fork 197
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
SOAP request fails #34
Comments
I have the same problem and have to go down the elements until I get to the element I want:
Here are some details about the problem: "The ‘gotcha’ moment with our response message is that the namespace “xmlns=http://ws.cdyne.com/WeatherWS/” does not have a prefix for the declaration. By not defining a prefix, it is defaulting to the default namespace or null namespace and we cannot use XPath expressions to reference the null namespace." |
Hi @mattt, What is the status of this issue? It seems like I'm experiencing it too. Regards, |
Apologies for not responding sooner, everyone. I'm not very familiar with SOAP, but I'd like to make any necessary fixes for this in code and/or documentation. I'll add the example you provided, @tosbaha, as a failing test case in a branch and work to figure out a solution.
In the meantime, have you tried calling the |
Sorry but this issue was so old. I don't work on this anymore. I think I made it work by stripping the name spaces. Since I don't have the old code anymore, I can't comment whether your workaround works or not. Cheers. |
I've tested this by calling |
For the following XML document(SOAP service), XPath can't find the elements.
Here are the result of some functions
Another example
Whenever there is nested namespaces, ono can't parse it. I don't know maybe it is limitation of libxml. Only workaround I found is to strip name spaces and other attributes.
The text was updated successfully, but these errors were encountered: