Come to think of it... you could do what I do at times. Half the time
people are giving me these LAME "wsdl" files for "web services" that
are NOT wsdl files that do NOT go with web services. They are only
"services" because they do NOT follow the specifications. .. so I ended
up writing my own webservice framework to deal with stuff like this...
at the heart of it was simple HTTP calls. You can do that too. If you
don't need https communication this is fairly easy. Web services are
really nothing more than XML going back and forth, you can do it all
manually if you want. It's not really that difficult.
That said... you really need to get on .NET 2.0 with WSE3 or get .NET
3.0. Using .NET 1.1 now adays just won't cut it...
Lee Franke wrote:
I am using a asmx page (framework 1.1).
I would think that as long as it is defined in the WSDL that the classes
would be generated.
Is that not correct?
Also what is WSE and WCF? DotNet technologies.
(bit of a newbie to the webservices).
thanks,
lee
"q" <ag******@gmail .comwrote in message
news:11******** **************@ h48g2000cwc.goo glegroups.com.. .
What webservices system are you using? ASMX? WSE? WCF?
You need WSE or WCF to do that... ASMX doesn't really support anything
but the most basic of webservices. They don't account for any of the
stronger specs.
Lee Franke wrote:
The application that I want to use requires the header to contain a
username/password.
Example:
<soap:Header>
<wsse:Securit y xmlns:wsse="htt p://schemas.xmlsoap .org/ws/2002/04/secext">
<wsse:UsernameT oken>
<wsse:Username> fluffy</wsse:Username>
<wsse:Passwor d Type="wsse:Pass wordText">bunny </wsse:Password>
</wsse:UsernameTo ken>
</wsse:Security>
</soap:Header>
The problem is that the WSDL of the webservice does not contain any
information reagarding this header information (shouldn't it?).
So when I add a web reference in my client application there is no class
reference to allow me to set the Username and Password for the header.
What (and how) do I need to modify for the class reference to appear?
Reference.cs? The WSDL itself then reimport? I can get it to work by
building the XML then just HTTP Post it to the URL, but I would rather
let
the program do it for me.
thanks,
lee