Office 2003 Web Services Toolkit issues

[Peter Rietkerk]

I have a few questions regarding the referencing of web services using this
toolkit. I am currently trying to reference a specific URL to WSDL that was
generated on a local server. Does anyone know of any issues in regards to
consuming WSDL for document-literal web services that define a lot of complex
types and/or import any other WSDL schema? I suspect that our WSDL might be
too sophisticated for the tool to handle. Maybe our use of the import
directive to bring in common schema types is confusing it. The WSDL is valid
because I am able to bring it up with Visual Studio .NET, and other tools do
not have any problems with it either (e.g. XMLSpy). Appreciate any feedback
on this one... thanks!
--
Peter Rietkerk

[[MSFT]]

Hello Peter,

I never heard a issue about Office 2003 Web Services Toolkit cannot
understand a WSDL schema. If the schema is validated, the Toolkit should
work with it. If you have any problem when you use it on your WSDL schema,
please post in the community. We will try to help you out.

Luke

[Peter Rietkerk]

Not sure how to do this. I cannot simply post an individual WSDL file because
it contains import statements for XML schema types, using schemaLocation
references which point back to my server. Again, Visual Studio .NET, XMLSpy,
..NET Webservice Studio 2.0, SOAPTest, Axis 1.2, etc. all work fine consuming
this WSDL and it's imported types, the Office 2003 Web Services Toolkit and
its predecessor products are the first tools we have encountered which do not
work with it. Can you confirm that the Office 2003 Web Services Toolkit tool
can handle WSDL which imports other schema? We know the WSDL and its
associated schema is valid, because it validates and all these other tools
consume it fine. Alternatively, how does one configure this thing to produce
any sort of diagnostic messages?? It just fails and doesn't produce any
meaningful output.
--
Peter Rietkerk
"[MSFT]" wrote:

Hello Peter,

I never heard a issue about Office 2003 Web Services Toolkit cannot
understand a WSDL schema. If the schema is validated, the Toolkit should
work with it. If you have any problem when you use it on your WSDL schema,
please post in the community. We will try to help you out

[[MSFT]]

Hi Peter,

Can you post the schema you used here so that I can test it on my side? Or
you send me an email. (Please remove "online" to get my actual email
address)

thanks,

Luke

[Peter Rietkerk]

thanks Luke, were you able to build a test case with the information on the
E-mail that I sent?
--
Peter Rietkerk
"[MSFT]" wrote:

Hi Peter,

Can you post the schema you used here so that I can test it on my side? Or
you send me an email. (Please remove "online" to get my actual email
address)

thanks,

Luke

[[MSFT]]

Hello Peter,

I haven't received the email from you yet. Can you send it again? (Please
remove "online." from my email address to ge actual one)

Thanks,

Luke

[Peter Rietkerk]

Tried to resend the E-mail, though it's the same address I used last time...
can you let me know if you have received it? thanks,
--
Peter Rietkerk
"[MSFT]" wrote:

Hello Peter,

I haven't received the email from you yet. Can you send it again? (Please
remove "online." from my email address to ge actual one)

Thanks,

Luke

[[MSFT]]

Hello Peter,

I test the wsdl file, it worked on my side. I think there are some issues
you may check:

1. I installed the latest Office Web Service Toolkit from this link:

http://msdn.microsoft.com/library/de...us/odc_wst2003
_ta/html/odc_WSTKNew.asp

2. I put the wsdl and xsd file in same virtual folder and rename
"http://..../common.xsd" to "contact.xs d" in wsdl file.
3. When open the files in VS.NET, I found some encoding problem, so that I
convert the two files to UTF-8 format.
I will appreciate if you can reply me on the newsgroup so that this can
benefit more people.

Regards,

Luke

[Peter Rietkerk]

Thanks for the assistance Luke.. I had actually generated that .wsdl file
from .NET WebService Studio by doing a "Save As", so there may have been some
encoding issues when that happened. Still, I need to ask why one tool (.NET
WebService Studio) is able to reference our specific URL
(http://localhost:12670/PWS/Contact?WSDL), and the Office 2003 Web Services
Toolkit cannot? Is it the fact that in the WSDL we have...
<?xml version="1.0" encoding="utf-16"?>
--
Cheers,
Peter Rietkerk
"[MSFT]" wrote:

Hello Peter,

I test the wsdl file, it worked on my side. I think there are some issues
you may check:

1. I installed the latest Office Web Service Toolkit from this link:

http://msdn.microsoft.com/library/de...us/odc_wst2003
_ta/html/odc_WSTKNew.asp

2. I put the wsdl and xsd file in same virtual folder and rename
"http://..../common.xsd" to "contact.xs d" in wsdl file.
3. When open the files in VS.NET, I found some encoding problem, so that I
convert the two files to UTF-8 format.
I will appreciate if you can reply me on the newsgroup so that this can
benefit more people.

Regards,

Luke

[[MSFT]]

Hi Peter,

I can reference the WSDL in both of Office 2003 Web Services Toolkit and
VS.NET. Have you installed the latest version of Office 2003 Web Services
Toolkit. From its document, it has fixed some problem on data type.

Luke