StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
4644015
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2011-01-10T05:45:14.603
FavoriteCount
0
LastActivityDate
2011-01-10T05:45:14.603
LastEditDate
LastEditorUserId
0
OwnerUserId
76337
ParentId
4642117
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
Try this: SimpleServiceSchema.xsd: <pre><code><xsd:schema targetNamespace="http://ttdev.com/ss/include" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <xsd:complexType name="concatRequestType"> <xsd:sequence> <xsd:element name="param1" type="xsd:string"/> <xsd:element name="param2" type="xsd:string"/> </xsd:sequence> </xsd:complexType> <xsd:complexType name="concatResponseType"> <xsd:sequence minOccurs="0" maxOccurs="100"> <xsd:element name="name" type="xsd:string"/> <xsd:element name="description" type="xsd:string"/> </xsd:sequence> </xsd:complexType> </xsd:schema> <wsdl:definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://ttdev.com/ss" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xi="http://www.w3.org/2001/XInclude" xmlns:inc="http://ttdev.com/ss/include" name="SimpleService" targetNamespace="http://ttdev.com/ss"> <wsdl:types> <xsd:schema targetNamespace="http://ttdev.com/ss"> <xsd:import namespace="http://ttdev.com/ss/include" schemaLocation="SimpleServiceSchema.xsd"/> <xsd:element name="concatRequest" type="inc:concatRequestType"/> <xsd:element name="concatResponse" type="inc:concatResponseType"/> </xsd:schema> </wsdl:types> <wsdl:message name="concatRequest"> <wsdl:part name="parameters" element="tns:concatRequest"/> </wsdl:message> <wsdl:message name="concatResponse"> <wsdl:part name="parameters" element="tns:concatResponse"/> </wsdl:message> <wsdl:portType name="SimpleService"> <wsdl:operation name="concat"> <wsdl:input message="tns:concatRequest"/> <wsdl:output message="tns:concatResponse"/> </wsdl:operation> </wsdl:portType> <wsdl:binding name="SimpleServiceSOAP" type="tns:SimpleService"> <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/> <wsdl:operation name="concat"> <soap:operation soapAction="http://ttdev.com/ss/NewOperation"/> <wsdl:input> <soap:body use="literal"/> </wsdl:input> <wsdl:output> <soap:body use="literal"/> </wsdl:output> </wsdl:operation> </wsdl:binding> <wsdl:service name="SimpleService"> <wsdl:port name="p1" binding="tns:SimpleServiceSOAP"> <soap:address location="http://localhost:8080/ss/p1"/> </wsdl:port> </wsdl:service> </wsdl:definitions> </code></pre> (thank you, XMLSpy)
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow do I decouple an embedded schema within a WSDL?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USJohn Saunders
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POHow do I decouple an embedded schema within a WSDL?
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COMaybe this is more an XML question than web service but why do you need to define the complexe type inside the schema and then define the actual element within the wsdl. Would it be posible to define the element inside the schema as well ?
 singulars
 PostPostId
 PO
 UserUserId
 USuser465374
2. CO@user: no, that's a WSDL question. The answer is that's the way they wrote it. And, no, in this case, you need the element to be in a namespace specific to the service. If used in a different service, it will be in a different namespace, yet will be of the same type.
 singulars
 PostPostId
 PO
 UserUserId
 USJohn Saunders

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.