Create proxy class from WSDL (.net & java)

[syed.ijaz]

Our company is doing a project for the City of Chicago and we are trying to communicate with their servers using web services. Their environment is java based but we are using .NET on our end. The problem we are currently facing right now is that we are not able to generate a proxy class using the wsdl they have provided us. This is the WSDL contract:
https://192.168.1.45/DataLink/ReceiveInterfaceAppUpdates.wsdl

wsdl.exe spits the following error when generating a proxy class out of this wsdl:
---
Microsoft (R) Web Services Description Language Utility
[Microsoft (R) .NET Framework, Version 1.0.3705.0]
Copyright (C) Microsoft Corporation 1998-2001. All rights reserved.

Schema validation warning: Namespace 'http://www.cityofchicago.org/csrinterface/request' is not available to be referenced in this schema.
Schema validation warning: The 'http://www.cityofchicago.org/csrinterface/request[IMG]http://www.thescripts.com/forum/images/smilies/biggrin.gif[/IMG]ocument' element is not declared.

Warning: Schema could not be validated. Class generation may fail or may produce incorrect results.

---

What is the reason for this error message and what is going wrong here?

[MattEvans]

That's not really an error so to speak; it's a message that says is "I looked at the URL http://www.cityofchicago.org/csrinterface/request to find a schema document to validate/process nodes under the namespace declared to conform to this schema; and I couldn't find one.)

If you change process specific namespaces to look for that URL as the schema, that would very probably cause an error. If you're just using a namespace to visually categorise a load of (your own) nodes; that's less likely to be critical; but you should probably define a valid schema for them to conform to.

Did an actual error occur?

[jwenting]

Often such warnings are harmless but they may result in specific services not being available (iow, methods and types that aren't mapped) or to compilation errors in the generated code.

Of course the actual WSDL is impossible for us to analyse here as you listed only a URI on your local network, unreachable from the internet.

You should also really upgrade to a more modern version of .NET. 1.0 is way outdated, 1.1 is the least you should use and most companies are using or planning to upgrade to 2.0.
The 2.0 wsdl parser is a lot better than the one in 1.1 (let alone 1.0) and is able to correctly parse wsdl that the older versions had problems with.