StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
14163660
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-01-04T19:32:56.720
FavoriteCount
0
LastActivityDate
2013-01-04T19:32:56.720
LastEditDate
LastEditorUserId
0
OwnerUserId
387927
ParentId
14160164
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
There is a casing issue in your WSDL. Instead of: <pre><code> <wsdl:message name="greetingResponse"> <wsdl:part type="tns:greeting" name="greetings"/> </wsdl:message> </code></pre> you should have: <pre><code> <wsdl:message name="greetingResponse"> <wsdl:part type="tns:Greeting" name="greetings"/> </wsdl:message> </code></pre> With this fixed, the following produces a web service that works fine when called from SOAPui: <pre><code><flow name="WS_In"> <http:inbound-endpoint address="http://localhost:8080/HelloService" exchange-pattern="request-response"> <cxf:proxy-service wsdlLocation="classpath:globalid3.wsdl" namespace="http://example.org/HelloService" service="ProxyService" /> </http:inbound-endpoint> <custom-processor class="com.example.ServiceProxy" /> </flow> </code></pre> Message processor: <pre><code>package com.example; import javax.xml.namespace.QName; import org.apache.commons.lang.StringEscapeUtils; import org.mule.api.MuleEvent; import org.mule.api.MuleException; import org.mule.api.processor.MessageProcessor; public class ServiceProxy implements MessageProcessor { private final static QName SIMPLE_GREETING = new QName("http://example.org/HelloService", "simpleGreeting"); public MuleEvent process(final MuleEvent event) throws MuleException { final QName operation = event.getFlowVariable("cxf_operation"); if (operation.equals(SIMPLE_GREETING)) { final String lastName = event.getMuleContext() .getExpressionLanguage() .evaluate("xpath('/lastName').text", event); final String responseXml = "<greetings><greet>Hi " + StringEscapeUtils.escapeXml(lastName) + "</greet></greetings>"; event.getMessage().setPayload(responseXml); return event; } throw new UnsupportedOperationException(operation.getLocalPart() + " " + operation.getNamespaceURI() + " " + operation.getPrefix()); } } </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POPlease advise on the WSDL
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USDavid Dossot
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POPlease advise on the 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
 VTUpMod
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
 VTAcceptedByOriginator
CommentsPostId
1. This table or related slice is empty.

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.