StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
2069474
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2010-01-15T04:14:51.640
FavoriteCount
0
LastActivityDate
2010-01-15T04:41:39.597
LastEditDate
2010-01-15T04:41:39.597
LastEditorUserId
48082
OwnerUserId
48082
ParentId
2013689
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
I don't know why WCF ignores XmlRoot, so I can't answer that part of your question. But I do have a couple ways to solve the problem. <ol> <li>start with WSDL first. If you have a particular set of XML namespaces you would like to apply to the messages that get sent and receieved, use WSDL and XML Schema to explicitly specify them. Then, generate the Server-side stub code, or the client-side proxy code, directly from that WSDL via <a href="http://msdn.microsoft.com/en-us/library/aa347733.aspx" rel="nofollow noreferrer">the svcutil.exe tool</a>. </li> <li><a href="http://blogs.msdn.com/dotnetinterop/archive/2007/07/19/interop-between-asmx-and-wcf-services.aspx" rel="nofollow noreferrer">use a custom ServiceHost</a> The other option open to you, described at <a href="http://blogs.msdn.com/dotnetinterop/archive/2007/07/19/interop-between-asmx-and-wcf-services.aspx" rel="nofollow noreferrer">this link</a>, is to use a custom ServiceHost that overrides WCF's decision to disregard the XmlRoot or XmlType attributes on message types. </li> </ol> <hr> If you choose to go for the WSDL-First approach, the WSDL should look like this: <pre><code><?xml version="1.0" encoding="utf-8" ?> <definitions xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="urn:The-Service-namespace" xmlns:tns="urn:The-Service-namespace" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:n0="urn:The-Request-namespace" xmlns:n1="urn:The-Response-namespace" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" elementFormDefault= "unqualified" > <types> <s:schema targetNamespace="urn:The-Request-namespace" > <s:complexType name="Type1"> <s:sequence> <s:element name="x" minOccurs="1" maxOccurs="1" type="s:string"/> </s:sequence> </s:complexType> <s:element name="Type1" type="n0:Type1" /> </s:schema> <s:schema targetNamespace="urn:The-Response-namespace" > <s:complexType name="Type2"> <s:sequence> <s:element name="x" minOccurs="1" maxOccurs="1" nillable="false" type="s:string"/> <s:element name="y" minOccurs="1" maxOccurs="1" nillable="false" type="s:int"/> <s:element name="z" minOccurs="1" maxOccurs="1" nillable="false" type="s:boolean" /> </s:sequence> </s:complexType> <s:element name="Type2" type="n1:Type2" /> </s:schema> </types> <message name="RequestMessage"> <part name="inPart1" element="n0:Type1" /> </message> <message name="ResponseMessage"> <part name="outPart1" element="n1:Type2" /> </message> <portType name="PortTypeName"> <operation name="Method1"> <input message="tns:RequestMessage" /> <output message="tns:ResponseMessage" /> </operation> </portType> <binding name="InterfaceName" type="tns:PortTypeName"> <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="rpc" /> <operation name="Method1"> <soap:operation soapAction="" style="document" /> <input> <soap:body use="literal" /> </input> <output> <soap:body use="literal" /> </output> </operation> </binding> </definitions> </code></pre> <hr> This WSDL is very simple - it defines a single operation, with a single request message and a single response message. Notice there are three xml namespaces: <ul> <li>urn:The-Service-namespace used for the element that wraps the request and response - the first element inside the <SOAP:body></li> <li>urn:The-Request-namespace used for the element wrapped inside that request wrapper, which gets deserialized into an instance of Type1. </li> <li>urn:The-Response-namespace used for the element wrapped inside that response wrapper, which gets deserialized into an instance of Type2.</li> </ul> If your web services interface is more complicated, has more operations and consequently more request and response message types, you can add more namespaces, if you like, for all those additional types. 
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWhy does the XmlRoot attribute gets ignored in WCF and how to overcome this
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USCheeso
UserOwnerUserId
1. USCheeso
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COThanks Cheeso. I am familiar with the custom host approach, and in fact - this is what we've done in a couple of places, but this seems to be a big ask, for a technology that carries the flag of interoperability. Anyway - the purpose of my question is to understand the behaviour. Appreciate you taking the time to answer.
 singulars
 PostPostId
 PO
 UserUserId
 USYossi Dahan

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.