Qualified elements in SOAP Body...

[J. Dudgeon]

Is it possible to configure a .NET 2.0 ASMX Web service to accept namespace
qualified messages?

For instance, instead of:

<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soap:Body>
<HelloRequest xmlns="http://foo/services/Test/HelloService">
<message>Wave</ns0:message>
<x>0</x>
<y>0</y>
<flag>none</flag>
</HelloRequest>
</soap:Body>
</soap:Envelope>

can an ASMX 2.0 Web service support:

<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:ns0="http://foo/services/Test/HelloService">
<soap:Body>
<ns0:HelloRequest>
<ns0:message>Wave</ns0:message>
<ns0:x>0</ns0:x>
<ns0:y>0</ns0:y>
<ns0:flag>none</ns0:flag>
</ns0:HelloRequest>
</soap:Body>
</soap:Envelope>

I know this is possible when working directly with the XmlSerializer, but
something isn't working in the Web service definition. I've even tried using
XmlElementAttribute(Form = XmlSchemaForm.Qualified) but that doesn't seem to
take.

I guess I could build an extension that performs the
serialization/deserialization instead of the default built-in code.

Thank you in advance,

Joel

[John Saunders]

"J. Dudgeon" <JD******@discussions.microsoft.comwrote in message
news:E6**********************************@microsof t.com...

Is it possible to configure a .NET 2.0 ASMX Web service to accept
namespace
qualified messages?

For instance, instead of:

<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soap:Body>
<HelloRequest xmlns="http://foo/services/Test/HelloService">
<message>Wave</ns0:message>
<x>0</x>
<y>0</y>
<flag>none</flag>
</HelloRequest>
</soap:Body>
</soap:Envelope>

All of these elements _are_ namespace-qualified.

John

[J. Dudgeon]

I understand that, but the test .NET Web service does not want to accept the
latter, even though they are theoretically equivalent. Therefore, if the
client puts the namespace/prefix declaration in the root of the envelope, it
breaks the service. One of our clients requested that we support:

<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:ns0="http://foo/services/Test/HelloService">
<soap:Body>
<ns0:HelloRequest>
<ns0:message>Wave</ns0:message>
<ns0:x>0</ns0:x>
<ns0:y>0</ns0:y>
<ns0:flag>none</ns0:flag>
</ns0:HelloRequest>
</soap:Body>
</soap:Envelope>

To repeat the question, is this possible?

"John Saunders" wrote:

"J. Dudgeon" <JD******@discussions.microsoft.comwrote in message
news:E6**********************************@microsof t.com...

Is it possible to configure a .NET 2.0 ASMX Web service to accept
namespace
qualified messages?

For instance, instead of:

<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soap:Body>
<HelloRequest xmlns="http://foo/services/Test/HelloService">
<message>Wave</ns0:message>
<x>0</x>
<y>0</y>
<flag>none</flag>
</HelloRequest>
</soap:Body>
</soap:Envelope>

All of these elements _are_ namespace-qualified.

John

[J. Dudgeon]

It turns out the error was a weird limitation in .NET Web services, it was a
formatting issue with the client request. I thought it was strange since
both requests are semantically equivalent.

"J. Dudgeon" wrote:

I understand that, but the test .NET Web service does not want to accept the
latter, even though they are theoretically equivalent. Therefore, if the
client puts the namespace/prefix declaration in the root of the envelope, it
breaks the service. One of our clients requested that we support:

<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:ns0="http://foo/services/Test/HelloService">
<soap:Body>
<ns0:HelloRequest>
<ns0:message>Wave</ns0:message>
<ns0:x>0</ns0:x>
<ns0:y>0</ns0:y>
<ns0:flag>none</ns0:flag>
</ns0:HelloRequest>
</soap:Body>
</soap:Envelope>

To repeat the question, is this possible?

"John Saunders" wrote:

"J. Dudgeon" <JD******@discussions.microsoft.comwrote in message
news:E6**********************************@microsof t.com...

Is it possible to configure a .NET 2.0 ASMX Web service to accept
namespace
qualified messages?
>
For instance, instead of:
>
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
>
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soap:Body>
<HelloRequest xmlns="http://foo/services/Test/HelloService">
<message>Wave</ns0:message>
<x>0</x>
<y>0</y>
<flag>none</flag>
</HelloRequest>
</soap:Body>
</soap:Envelope>

All of these elements _are_ namespace-qualified.

John

[John Saunders]

"J. Dudgeon" <JD******@discussions.microsoft.comwrote in message
news:D1**********************************@microsof t.com...

>I understand that, but the test .NET Web service does not want to accept
the
latter, even though they are theoretically equivalent. Therefore, if the
client puts the namespace/prefix declaration in the root of the envelope,
it
breaks the service. One of our clients requested that we support:

Sorry, you're mistaken. They aren't _theoretically_ equivalent, they _are_
equivalent.

You should start from the assumption that they are the same and then figure
out how, if they're the same, could you be getting the results you're
experiencing.

One thing to do as a diagnostic tool would be to put the problematic XML
into a file and read it into an XmlDocument. Then look at each node to see
what the LocalName and NamespaceUri are set to.

John

[John Saunders]

"J. Dudgeon" <JD******@discussions.microsoft.comwrote in message
news:D0**********************************@microsof t.com...

It turns out the error was a weird limitation in .NET Web services, it was
a
formatting issue with the client request. I thought it was strange since
both requests are semantically equivalent.

Can you please post an example of the bad vs. good XML?

John

[J. Dudgeon]

Sorry, the above post should have read "It turns out it *wasn't* a strange
limitation in the .NET Web service." It ended up being a client problem.

Unfortunately, I can't post what they sent because the trace file of the
incoming SOAP messages was cleared before I could save it.

Another project team ran into an issue back in 2001/2002 with a .NET Web
service not correctly deserializing the XML stream and it was related to the
location of namespace declarations. I don't recall the specifics but I
believe it was fixed by using the XmlTextReader or the XmlDocument class to
directly deserialize the XML stream.

As for my use of "theoretical", it was more slang for "supposed to be"; i.e.
"even though they are *supposed to be* equivalent". My bad.

"John Saunders" wrote:

"J. Dudgeon" <JD******@discussions.microsoft.comwrote in message
news:D1**********************************@microsof t.com...

I understand that, but the test .NET Web service does not want to accept
the
latter, even though they are theoretically equivalent. Therefore, if the
client puts the namespace/prefix declaration in the root of the envelope,
it
breaks the service. One of our clients requested that we support:

Sorry, you're mistaken. They aren't _theoretically_ equivalent, they _are_
equivalent.

You should start from the assumption that they are the same and then figure
out how, if they're the same, could you be getting the results you're
experiencing.

One thing to do as a diagnostic tool would be to put the problematic XML
into a file and read it into an XmlDocument. Then look at each node to see
what the LocalName and NamespaceUri are set to.

John