Well, I must say THANK YOU! for getting me going on this... I do have another question though. > I have to ask: why do you need to work directly with sockets? > Do you have some requirement that you cannot use a SOAP library? I guess, I could use the library. I was given some sample programs that used sockets and that's what I started playing with...
> Your SOAP payload should look something like > > <?xml version='1.0' encoding='UTF-8'?> > <SOAP-ENV:Envelope > xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"; > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xmlns:xsd="http://www.w3.org/2001/XMLSchema";> > <SOAP-ENV:Body> > <ns1:getMeaning xmlns:ns1="urn:XcelXmlServer" > > SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";> > <wordToLookup xsi:type="xsd:string">toughWord</wordToLookup> > </ns1:getMeaning> > </SOAP-ENV:Body> > </SOAP-ENV:Envelope> This works just fine. Thanks again but, my (SOAP) clients are sending me (the SOAP server) an xml file wrapped in an SOAP envelope as follows. How do I know what service they are requesting? And, what params they have sent? <?xml version="1.0"?> <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/";> <env:Header/> <env:Body> <SubmitRequest xmlns="http://abc.def.ghi/jkl/mno"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://abc.def.ghi/jkl/xyz.xsd";> <DefaultStatus location="SOME LOCATION"> <ResourceStatus>OutAndOver</ResourceStatus> </DefaultStatus> </SubmitRequest> </env:Body> </env:Envelope> Or in other words, how do the above two co-relate? The first xml payload has <ns1:getMeaning xmlns:ns1="urn:XcelXmlServer" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";> <wordToLookup xsi:type="xsd:string">toughWord</wordToLookup> </ns1:getMeaning> that tells the server what service and params it is sending. How is the same achieved in second xml file? -Nishi
