There are a couple of things you can do.
WSE2 includes the ability to call Web Services dynamically without a proxy object. However, I think it still needs a WSDL file, so I'm not sure if that'll work.
Christian Weyer and friends also have a tool for dynamically calling Web Services DynWSLib 1.5 but I think it too requires WSDL. There maybe routines though for directly activating an endpoint.
http://www.thinktecture.com/Resources/Software/default.htmlI haven't used either of these tools but I've been thinking about this for a while.
Honestly though, this is a broken implmentation. If there's no WSDL it's not really a Web Service <g> and you're getting sold short.
If worse comes to worse you can always just fire off the XML you need manually and use code to gen the XML. Given that there is no service description this sort of makes sense.
+++ Rick ---
>A company I'm working with created a web service to access their data. They did not create a complete WSDL (they're using Eclipse and Apache), though, and they apparently don't intend to. The result is that when I add the web service to the .Net project, not all the necessary pieces are accesible in code.
>
>In particular, I need to pass data through the SOAP message header, and apparently, since the header is not described, it's not accessible (see my other post).
>
>.Net is not giving me access to the header when I add a reference to it.
>
>I believe that if I create the web service client using the .Net framework classes rather than as a reference to the project, that I can get around this by manually creating the SOAP header. I can't figure out which classes to use, though. I see references in the documentation, but every example I find relies on adding the web service as a project reference.
>
>Any thoughts or ideas on where to look would be greatly appreciated!
>
>My alternative is to create the code in Java using Eclipse, because I have sample working Java code. Eclipse ain't my thing, though, so I'd love to keep it in .Net.
>
>Thanks,
>
>David
