XML Editor
Sign up for a WebBoard account Sign Up Keyword Search Search More Options... Options
Chat Rooms Chat Help Help News News Log in to WebBoard Log in Not Logged in
Show tree view Topic
Topic Page 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 Go to previous topicPrev TopicGo to next topicNext Topic
Postnext
bill darcySubject: Web Service Call tester
Author: bill darcy
Date: 03 Nov 2009 04:36 PM
using Stylus Studio 2010 Enterprise, when i create a new Web Service Call to the WSDL URL http://www.xignite.com/xGlobalQuotes.asmx?WSDL SS opens the Web Service Call Composer/Tester just as in the helpful http://www.stylusstudio.com/ws_tester.html.

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?

thanks.

Postnext
Ivan PedruzziSubject: Web Service Call tester
Author: Ivan Pedruzzi
Date: 04 Nov 2009 12:14 PM
Hi Bill,

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


Thanks!
Ivan Pedruzzi
Stylus Studio Team

Postnext
bill darcySubject: 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.


UnknownServices.wsdl
Exchange 2007 Services.wsdl

Postnext
bill darcySubject: 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.

Postnext
bill darcySubject: Web Service Call tester
Author: bill darcy
Date: 10 Nov 2009 03:18 PM
is that "1998" namespace url the cause of the problem? is there any setting to tell SoapUI to not care about this?

thanks.

Postnext
Ivan PedruzziSubject: Web Service Call tester
Author: Ivan Pedruzzi
Date: 11 Nov 2009 12:16 PM
Bill,

Could you try to create a Web Service Call to the following WSDL and tell us if works for you?

http://localhost/namespace/wsdl

Thanks!
Ivan Pedruzzi
Stylus Studio Team

Postnext
bill darcySubject: 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?

Postnext
Ivan PedruzziSubject: Web Service Call tester
Author: Ivan Pedruzzi
Date: 11 Nov 2009 02:21 PM

Sorry it was the wrong WSDL URL, use this

http://examples.xquery.com/namespace/wsdl

This is a test service that imports a schema that uses

<xsd:import namespace="http://www.w3.org/XML/1998/namespace"/>

it seems to work fine here

Postnext
bill darcySubject: Web Service Call tester
Author: bill darcy
Date: 11 Nov 2009 04:21 PM

>http://examples.xquery.com/namespace/wsdl

that works fine. one difference is that this example contains
<xsd:import namespace="http://www.w3.org/XML/1998/namespace"/>

while the Exchange Servcies.wsdl contains
<xs:import namespace="http://www.w3.org/XML/1998/namespace"/>

does xs:import specify to SS to fetch that xsd while parsing the original wsdl file while xsd:import does not? i dont know enough about xsd etal.


Postnext
Ivan PedruzziSubject: Web Service Call tester
Author: Ivan Pedruzzi
Date: 11 Nov 2009 05:24 PM

The difference in the prefixes (xs vs xsd) doesn't matter as long as they are bound to the same namespace http://www.w3.org/2001/XMLSchema

The reason why you are getting an error has to be something else

Ivan Pedruzzi
Stylus Studio Team

Postnext
bill darcySubject: 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.

thanks for your help so far.

Postnext
bill darcySubject: 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.

Postnext
Alberto MassariSubject: Web Service Call tester
Author: Alberto Massari
Date: 12 Nov 2009 12:47 PM
Hi Bill,
if you can change the WSDL to have a schemaLocation="http://www.w3.org/2001/xml.xsd", that would definitely help fixing the problem.

Alberto

Posttop
Shawn MowerSubject: Web Service Call tester
Author: Shawn Mower
Date: 08 Sep 2010 12:26 PM
Hello,

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.

Thanks!
Shawn

 
Topic Page 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 Go to previous topicPrev TopicGo to next topicNext Topic
Download A Free Trial of Stylus Studio 6 XML Professional Edition Today! Powered by Stylus Studio, the world's leading XML IDE for XML, XSLT, XQuery, XML Schema, DTD, XPath, WSDL, XHTML, SQL/XML, and XML Mapping!  
go

Log In Options

Site Map | Privacy Policy | Terms of Use | Trademarks
Stylus Scoop XML Newsletter:
W3C Member
Stylus Studio® and DataDirect XQuery ™are from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2016 All Rights Reserved.