however, when i create new Web Service Call to the url for our Exchange 2007 server (http://10.111.16.22/ews/Services.wsdl) SS opens the WSDL Editor instead of the Tester.
how can i get SS to open the Tester for our Exchange 2007 WSDL?
Subject:Web Service Call tester Author:bill darcy Date:04 Nov 2009 01:18 PM
>Could you confirm if these are the steps you are taking?
>
>- File -> New -> Web Service Call
>- Set WSDL URL to http://10.111.16.22/ews/Services.wsdl
yup.
when i paste the WSDL URL and press Enter an error dialog is displayed with the message "grammar not found for namespace 'http://www.w3.org.XML/1998/namespace'.
when i click the View WSDL document button i'm prompted for credentials and it displays the WSDL in the editor. i dont find the namespace its complaining about in the retrieved WSDL. its the standard Services.wsdl from an Exchange2007 server. its attached (saved from SS after retrieving from the server). is there something in this wsdl that SS doesn't like. i wouldnt be surprised if Microsoft did somethnig a little different.
Subject:Web Service Call tester Author:bill darcy Date:04 Nov 2009 01:40 PM
a little more digging using Wireshark to watch the traffic shows that SS not only retrieves the WSDL (that i attached), but it continues to retrieve XSD files referenced in the WSDL. /ews/types.xsd includes the line
<xs:import namespace="http://www.w3.org/XML/1998/namespace"/>
where
xmlns:xs="http://www.w3.org/2001/XMLSchema"
does SS try to load that namespace file? i can retrieve it in a browser, but its HTML not XML.
Subject:Web Service Call tester Author:bill darcy Date:11 Nov 2009 01:37 PM
i'm running SS on my development system which has no web server running on it. as expected your url does not work. i am trying to use SS to test the web services on a Microsoft Exchange server (the WSDL url in a prev post) that's running on another computer.
Wireshark shows me that SS gets the initial WSDL file correctly, then retrieves the various xsd files referenced in the WSDL. it seems to encounter a problem when one of the referenced xsd files is different than expected (see prev post). is there any way to tell SS to not be so thorough or continue despite the failure to retrieve one xsd file?
Subject:Web Service Call tester Author:bill darcy Date:12 Nov 2009 12:15 PM
any idea what else it would be? maybe its particular to the Exchange 2007 WSDL. that and the imported namespaces are attached to a previous post. it wouldn't surprise me if MS did something non-standard.
none of our Exchange 2007 servers (where this WSDL came from) are outside our firewall for you to access. you dont have access to an Exchange 2007 server to see this yourself, do you? i was unable to find a free trial from a hosting company that didn't require me to use my domain and credit card.
Subject:Web Service Call tester Author:bill darcy Date:12 Nov 2009 12:20 PM
i wonder if its because the offending
<xs:import namespace="http://www.w3.org/XML/1998/namespace"/>
lacks a schemaLocation attribute? it appears to be the only xs:import element like that.
Did you ever get this problem fixed? I am having the same issue. Please let me know if a resolution was discovered and specifically what to do to fix it.