It looks then that the external application might not be sending enough
information to make your webservice tick - have you disabled get and post
yet in your webservice config to see if it accepts the envelope?
Here is an example of a full xml soap envelope destned for a .NET
webservice, for a simple hello world example.
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
SOAP-ENV:encodingStyle=
"http://schemas.xmlsoap.org/soap/encoding/"
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/1999/XMLSchema">
<SOAP-ENV:Header>
<MyHeader xmlns="http://www.alfredbr.com/">
<MyName xsi:type="xsd:string">Alfred</MyName>
</MyHeader>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
<namesp1:HelloWorld2 xmlns:namesp1="http://www.alfredbr.com/"/>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Its quite different to that which you are recieving - you might therefore
have to modify your service, or get them to modify their request. From your
example, your a and b types are not defined so the webservice might simply
reject them as not being wsdl 1.1 compliant.
There is a utility at
http://www.gotdotnet.com/team/tools/web_svc/ that
allows you to create and debug soap traffic to see why yours wont work.
I've not tried it, but it requires no code from what I gather, so its
probably a great test utility to work out where your problem is.
As I said, I've not done any soap request from none .NET clients for quite
some time so I dont have an easy answer for you, I hope that helps anyway.
--
Regards
John Timney
ASP.NET MVP
Microsoft Regional Director
"author" <no**@available.com> wrote in message
news:m2********************************@4ax.com...
I think you might be looking for the wrong thing.
I dont recall that you need to construct an actual soap envelope
Some external application, without my control is sending soap-xml, so
it have to been in that way.