Re: SOAP:Lite Client .NET Server problem
- --- In email@example.com, "m_gladding" <mgladding@w...> wrote:
> Any idea now? The only differences between how SOAP::Lite sends theare
> SOAP Statement and how the .Net application expects to receive it
> as follows:Since the namespaces *DO* differ, I'm sure that's bound to make a
> SOAP::Lite has <soap:Envelope xmlns:xsi="http://www.w3.or
> xmlns:xsd="http://www.w3.org/1999/XMLSchema" soap:enc
> for it's envelope tag... take note of the years (1999) and also the
> encodingStyle Tag.
> This is how the .Net server expects the envelope tag to be:
> <soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> Note the year is now 2001 for the schema stuff, and there is no
> Does anyone know if any of this would make a difference?
difference somewhere. http://www.w3.org/1999/XMLSchema and
http://www.w3.org/2001/XMLSchema (as well as the other difference)
are two different strings. Therefore, they are two different XML
There's a chance that the two URLs do point to something, but that's
merely a coincidence.
If you can get the namespaces to match exactly, then I think you
*MAY* have better results. Don't quote me, though, as I am still
learning, myself. (Anyone care to correct me? Does the problem here
More information on XML namespaces: