Cannot find dispatch method for {http://www.ivan.com/additionservicetypes}addValuesRequest

[Mark Heron]

Hello Folks,

I'm trying example of document style webservice from Ivan's study guide section 9.3. On running client program I'm getting below error.

Adding the values 7.241783721362973 and 1.5793153077945998:
*** A fatal error occurred:
Cannot find dispatch method for {http://www.ivan.com/additionservicetypes}addValuesRequest

SOAP request on TCPMon:

POST /JAX-WS_SchemaToWS/calculationService HTTP/1.1
Content-type: text/xml;charset="utf-8"
Soapaction: "http://www.ivan.com/AdditionService/CalculationService/addValuesRequest"
Accept: text/xml, multipart/related, text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
User-Agent: JAX-WS RI 2.1.6 in JDK 6
Host: 127.0.0.1:37199
Connection: keep-alive
Content-Length: 283

<?xml version="1.0" ?>

<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<S:Body>
<ns2:addValuesRequest xmlns:ns2="http://www.ivan.com/additionservicetypes">
<value1>7.241034568984911</value1>
<value2>1.5627112561036527</value2>
</ns2:addValuesRequest>
</S:Body>
</S:Envelope>

SOAP response on TCPMon:

HTTP/1.1 500 Internal Server Error
X-Powered-By: Servlet/3.0
Server: GlassFish v3
Content-Type: text/xml;charset=utf-8
Transfer-Encoding: chunked
Date: Thu, 19 Aug 2010 16:33:16 GMT
Connection: close

6e
<?xml version='1.0' encoding='UTF-8'?>
<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<S:Body>
f1
<S:Fault xmlns:ns4="http://www.w3.org/2003/05/soap-envelope">
<faultcode>S:Client</faultcode>
<faultstring>Cannot find dispatch method for {http://www.ivan.com/additionservicetypes}addValuesRequest
</faultstring>
</S:Fault>
</S:Body>
</S:Envelope>
0

Does anybody get similar error? Any idea what can be the solution?

Thanks

[Ivan Krizsan]

Hi!
Please enclose the WSDL and XSD for the service you have developed.
Have you tried to send requests to the service using soapUI?
Best wishes!

[Mark Heron]

Here you go. I have to modify additionType.xsd to additionTypes.xsd(extra "s" in name) to locate XSD correctly. I assume it is typo in study guide.(Version: July 12, 2010)

==================================================================================================================
WSDL
==================================================================================================================

<?xml version="1.0" encoding="UTF-8"?>
<!--
WSDL file for the addition service.
-->
<wsdl:definitions
        xmlns:tns="http://www.ivan.com/AdditionService"
        xmlns:types="http://www.ivan.com/additionservicetypes"
        xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
        xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
        xmlns:xsd="http://www.w3.org/2001/XMLSchema"
        name="AdditionService"
        targetNamespace="http://www.ivan.com/AdditionService"
        xsd:schemaLocation="http://www.ivan.com/additionservicetypes additionTypes.xsd">
    <!--
    Here we import the schema containing the request and
    response types of the operation(s) in the web service.
    -->
    <wsdl:types>
        <xsd:schema>
            <xsd:import namespace="http://www.ivan.com/additionservicetypes"
                        schemaLocation="additionTypes.xsd"/>
        </xsd:schema>
    </wsdl:types>
    <!--
    This message holds input data to the addValues operation.
    -->
    <wsdl:message name="additionRequest">
        <wsdl:part name="params" element="types:addValuesRequest"/>
    </wsdl:message>
    <!--
    This message holds output data from the addValues operation.
    -->
    <wsdl:message name="additionResponse">
        <wsdl:part name="result" element="types:addValuesResponse"/>
    </wsdl:message>
    <!--
    This message holds data of a fault generated by the addValues operation.
    -->
    <wsdl:message name="additionFault">
        <wsdl:part name="error" element="types:addValuesFault"/>
    </wsdl:message>
    <!--
    This is the abstract interface of the web service.
    It only contains one single operation, addValues.
    -->
    <wsdl:portType name="calculationPortType">
        <wsdl:operation name="addValues">
            <wsdl:input message="tns:additionRequest"/>
            <wsdl:output message="tns:additionResponse"/>
            <wsdl:fault name="error" message="tns:additionFault"/>
        </wsdl:operation>
    </wsdl:portType>
    <!--
    Binding for the calculationPortType, specifying
    Document/Literal over HTTP.
    -->
    <wsdl:binding name="calculationBinding" type="tns:calculationPortType">
        <soap:binding
                transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
        <wsdl:operation name="addValues">
            <soap:operation soapAction="urn:addValues"/>
            <wsdl:input>
                <soap:body use="literal"/>
            </wsdl:input>
            <wsdl:output>
                <soap:body use="literal"/>
            </wsdl:output>
            <wsdl:fault name="error">
                <soap:fault name="error" use="literal"/>
            </wsdl:fault>
        </wsdl:operation>
    </wsdl:binding>
    <!--
    Finally, this is the declaration of the concrete calculationService.
    If the web service is going to be deployed in GlassFish, then there
    is no need to set the location attribute of the <soap:address> element
    since GlassFish will take care of this when the service is being
    deployed.
    -->
    <wsdl:service name="calculationService">
        <wsdl:port name="calculationServicePort"
                   binding="tns:calculationBinding">
            <soap:address location="TBA"/>
        </wsdl:port>
    </wsdl:service>
</wsdl:definitions>

==================================================================================================================
XSD
==================================================================================================================

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<xs:schema xmlns:tns="http://www.ivan.com/additionservicetypes"
           xmlns:xs="http://www.w3.org/2001/XMLSchema"
           targetNamespace="http://www.ivan.com/additionservicetypes" version="1.0">
    <!--
    The addValuesRequest element holds the parameters of the
    request to the web service to add two numbers.
    -->
    <xs:element name="addValuesRequest">
        <xs:complexType>
            <xs:sequence>
                <xs:element name="value1" type="xs:double"/>
                <xs:element name="value2" type="xs:double"/>
            </xs:sequence>
        </xs:complexType>
    </xs:element>
    <!--
    The addValuesResponse element holds the result of a
    request to the web service to add two numbers.
    -->
    <xs:element name="addValuesResponse">
        <xs:complexType>
            <xs:sequence>
                <xs:element name="sum" type="xs:double"/>
            </xs:sequence>
        </xs:complexType>
    </xs:element>
    <!--
    The addValuesFault element holds data about error
    that occurred adding values.
    -->
    <xs:element name="addValuesFault">
        <xs:complexType>
            <xs:sequence>
                <xs:element name="errorMsg" type="xs:string"/>
                <xs:element name="value1" type="xs:double"/>
                <xs:element name="value2" type="xs:double"/>
            </xs:sequence>
        </xs:complexType>
    </xs:element>
</xs:schema>

I also tried to send requests using aoapUI. I got similar response. See below.
==================================================================================================================
soapUI Request
==================================================================================================================

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:add="http://www.ivan.com/additionservicetypes">
   <soapenv:Header/>
   <soapenv:Body>
      <add:addValuesRequest>
         <value1>56.9384</value1>
         <value2>93.70</value2>
      </add:addValuesRequest>
   </soapenv:Body>
</soapenv:Envelope>

==================================================================================================================
soapUI Response
==================================================================================================================

<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
   <S:Body>
      <S:Fault xmlns:ns4="http://www.w3.org/2003/05/soap-envelope">
         <faultcode>S:Client</faultcode>
         <faultstring>Cannot find dispatch method for {http://www.ivan.com/additionservicetypes}addValuesRequest</faultstring>
      </S:Fault>
   </S:Body>
</S:Envelope>

[Ivan Krizsan]

Hi!

Mark Heron wrote:Here you go. I have to modify additionType.xsd to additionTypes.xsd(extra "s" in name) to locate XSD correctly. I assume it is typo in study guide.(Version: July 12, 2010)

Indeed! Thank you for pointing this out!

I pasted the WSDL and the XML schema into my version of the web service and it does look like there are no problems with those two files, since the web service works as expected.
I did generate the JAXB bean classes etc using the Ant-script.
I tried with soapUI and received this response:

<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
   <S:Body>
      <ns3:addValuesResponse xmlns:ns2="http://www.ivan.com/additionservicetypes" xmlns:ns3="http://www.ivan.com/AdditionService">
         <sum>150.6384</sum>
      </ns3:addValuesResponse>
   </S:Body>
</S:Envelope>

If you want me to look further into this, please compress the entire web service project in an archive file and put it somewhere where I can download it.
Best wishes!

[Mark Heron]

Ivan,

Thanks for looking into this. I appreciate your help.

Can you please provide me corresponding HTTP(NOT SOAP) request? Also, Please let me know Glassfish and soapUI version you are using.

I noticed one thing, I can successfully test my webservice using Glassfish test tool. However, it uses diffrent SOAP request than what soapUI and standalone client is using. Moreover, when I compare WSDL within my webservice project with Glassfish version of WSDL they are diffrent in Action and operation name. I guess Glassfish generates WSDL out of implementation class and it doesn't care what mapping is defined within WSDL inside WEB-INF/wsdl folder. I wish Glassfish can validate class and WSDL at deploy time and flag error if something is not matching rather than silently generating own version of wsdl and use it.

Thanks
Mark

[Ivan Krizsan]

Hi!
If GlassFish generates a WSDL instead of using the existing one, then make sure that the endpoint implementation class is properly annotated:

@WebService( name = "CalculationService", targetNamespace = "http://www.ivan.com/AdditionService", serviceName = "calculationService", portName = "calculationServicePort", wsdlLocation = "WEB-INF/wsdl/AdditionService.wsdl")
@SOAPBinding(parameterStyle = SOAPBinding.ParameterStyle.BARE) @XmlSeeAlso({ObjectFactory.class})
public class CalculationImpl implements CalculationPortType

I'll get back later with more information and sample request.
Best wishes!

[Ivan Krizsan]

Hi!
Sorry about the delay.
First of all, I use GlassFish 3.0.1 but originally when developing the sample, I used GlassFish 2.1.
For testing, I have used soapUI 3.5.
I can only supply the request generated by soapUI, which looks like this:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:add="http://www.ivan.com/additionservicetypes">
   <soapenv:Header/>
   <soapenv:Body>
      <add:addValuesRequest>
         <value1>5.13</value1>
         <value2>7.96</value2>
      </add:addValuesRequest>
   </soapenv:Body>
</soapenv:Envelope>

The corresponding response looks like this:

<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
   <S:Body>
      <ns3:addValuesResponse xmlns:ns2="http://www.ivan.com/additionservicetypes" xmlns:ns3="http://www.ivan.com/AdditionService">
         <sum>13.09</sum>
      </ns3:addValuesResponse>
   </S:Body>
</S:Envelope>

Best wishes!

[Mark Heron]

Ivan,

Finally, it worked. I was using GlassFishV3 application server. When I moved same code to GlassFish 3.0.1, it worked like charm. Funny Right? The core idea of Webservice is interoperability but it doesn't seem to be portable between two versions of same server.

Anyways, Thanks a lot for your quick followup.

Thanks

[Ivan Krizsan]

Hi!
Good to hear that the matter is resolved.
Did you use v3 or v3 prelude before switching to v3.0.1?
Best wishes!

[Mark Heron]

Ivan,

I used GlassFish V3(Sun) before switch to V3.0.1(Oracle).

Regards