Databases
StackOverflow2013
Postsdbo
POPlease advise on the WSDL
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POPlease advise on the WSDL
    primarykey
    data
    text
    <p>I have created a WSDL to create a greeting service. Given below is the WSDL. </p> <p>I am using thsi wsdl to create a generate and expose a web-service using the cxf:proxy-service in mule. </p> <p>This is giving me errors.</p> <p>Please review and help me undertand what is the problem with this WSDL.</p> <pre><code>&lt;?xml version='1.0' encoding='UTF-8'?&gt; &lt;wsdl:definitions name="HelloService" targetNamespace="http://example.org/HelloService" xmlns:tns="http://example.org/HelloService" xmlns:ns1="http://schemas.xmlsoap.org/soap/http" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema"&gt; &lt;wsdl:types&gt; &lt;xsd:schema targetNamespace="http://example.org/HelloService" &gt; &lt;xsd:element name="LastName"&gt; &lt;xsd:complexType&gt; &lt;xsd:sequence&gt; &lt;xsd:element name="lName" type="xsd:string"/&gt; &lt;/xsd:sequence&gt; &lt;/xsd:complexType&gt; &lt;/xsd:element&gt; &lt;xsd:element name="FirstName"&gt; &lt;xsd:complexType&gt; &lt;xsd:sequence&gt; &lt;xsd:element name="fName" type="xsd:string"/&gt; &lt;/xsd:sequence&gt; &lt;/xsd:complexType&gt; &lt;/xsd:element&gt; &lt;xsd:element name="Greeting"&gt; &lt;xsd:complexType&gt; &lt;xsd:sequence&gt; &lt;xsd:element name="greet" type="xsd:string"/&gt; &lt;/xsd:sequence&gt; &lt;/xsd:complexType&gt; &lt;/xsd:element&gt; &lt;/xsd:schema&gt; &lt;/wsdl:types&gt; &lt;wsdl:message name="shortRequest"&gt; &lt;wsdl:part type="tns:LastName" name="lastName"/&gt; &lt;/wsdl:message&gt; &lt;wsdl:message name="fullRequest"&gt; &lt;wsdl:part type="tns:FirstName" name="firstName"/&gt; &lt;wsdl:part type="tns:LastName" name="lastName"/&gt; &lt;/wsdl:message&gt; &lt;wsdl:message name="greetingResponse"&gt; &lt;wsdl:part type="tns:greeting" name="greetings"/&gt; &lt;/wsdl:message&gt; &lt;wsdl:portType name="HelloServicePortType"&gt; &lt;wsdl:operation name="simpleGreeting"&gt; &lt;wsdl:input message="tns:shortRequest" name="shortRequest" /&gt; &lt;wsdl:output message="tns:greetingResponse" name="greetingResponse" /&gt; &lt;/wsdl:operation&gt; &lt;wsdl:operation name="fullGreeting"&gt; &lt;wsdl:input message="tns:fullRequest" name="fullRequest" /&gt; &lt;wsdl:output message="tns:greetingResponse" name="greetingResponseFull" /&gt; &lt;/wsdl:operation&gt; &lt;/wsdl:portType&gt; &lt;wsdl:binding name="HelloServiceSOAP" type="tns:HelloServicePortType"&gt; &lt;soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/&gt; &lt;wsdl:operation name="simpleGreeting"&gt; &lt;soap:operation soapAction="" style="document" /&gt; &lt;wsdl:input name="shortRequest"&gt; &lt;soap:body use="literal"/&gt; &lt;/wsdl:input&gt; &lt;wsdl:output name="greetingResponse"&gt; &lt;soap:body use="literal"/&gt; &lt;/wsdl:output&gt; &lt;/wsdl:operation&gt; &lt;wsdl:operation name="fullGreeting"&gt; &lt;soap:operation soapAction="" style="document" /&gt; &lt;wsdl:input name="fullRequest"&gt; &lt;soap:body use="literal"/&gt; &lt;/wsdl:input&gt; &lt;wsdl:output name="greetingResponseFull"&gt; &lt;soap:body use="literal"/&gt; &lt;/wsdl:output&gt; &lt;/wsdl:operation&gt; &lt;/wsdl:binding&gt; &lt;wsdl:service name="ProxyService"&gt; &lt;wsdl:port binding="tns:HelloServiceSOAP" name="HelloServiceSOAPB"&gt; &lt;soap:address location="http://localhost:8080/HelloService" /&gt; &lt;/wsdl:port&gt; &lt;/wsdl:service&gt; &lt;/wsdl:definitions&gt; </code></pre> <p>Please help me if there is something wrong in my WSDL. It is not working when I use it in mule cxf:proxy-service.</p> <p>FGiven below si the Mule Flow which is using this WSDL to expose service.</p> <pre><code>&lt;flow name="WS_In"&gt; &lt;http:inbound-endpoint address="http://localhost:8080/HelloService" exchange-pattern="request-response"&gt; &lt;cxf:proxy-service wsdlLocation="classpath:globalid3.wsdl" namespace="http://example.org/HelloService" service="ProxyService" /&gt; &lt;/http:inbound-endpoint&gt; &lt;component&gt; &lt;prototype-object class="com.example.ServiceProxy"&gt; &lt;/prototype-object&gt; &lt;/component&gt; &lt;echo-component&gt;&lt;/echo-component&gt; &lt;logger level="INFO" /&gt; &lt;/flow&gt; </code></pre> <p>and the Error is : </p> <pre><code>org.mule.api.lifecycle.LifecycleException: Lifecycle Manager 'WS_In.stage1' phase 'start' does not support phase 'dispose' at org.mule.lifecycle.AbstractLifecycleManager.invokePhase(AbstractLifecycleManager.java:156) </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USuser1760178
    1. USuser1760178
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POPlease advise on the WSDL
      1. This table or related slice is empty.
      1. VTUpMod
    1. COPlease provide more information about the error you are getting and how you are consuming the web service.
      singulars
      1. POPlease advise on the WSDL
      1. USgenjosanzo
    2. COAlso: why using a `prototype-object`? Do you really want a new instance created for each request?
      singulars
      1. POPlease advise on the WSDL
      1. USDavid Dossot
    3. COyes. I am looking for new object for each request. I got it working. The problem is with the WSDL I guess. Given below is the answer.
      singulars
      1. POPlease advise on the WSDL
      1. USuser1760178
 

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.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload