What's Wrong with this simple WSDL

[Avinash Ga]

Hi Ranchers,

I have written a contract first web service (its my first TOOO )..... i have deployed the same in glass fish server and when i try to invoke the service using jax-ws generated client im getting this exception
. i also tried creating a soapui project using the same wsdl, but unable to generate the sample request.

Exception in thread "main" javax.xml.ws.soap.SOAPFaultException: Cannot find dispatch method for {http://www.example.org/PersonService/}personRequest
at com.sun.xml.internal.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:178)
at com.sun.xml.internal.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:111)
at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:108)
at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:78)
at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(SEIStub.java:107)
at $Proxy29.getPerson(Unknown Source)
at org.example.personservice.PersonServiceTester.main(PersonServiceTester.java:17)


here is my wsdl.....


<?xml version="1.0" encoding="UTF-8" standalone="no"?> <wsdl:definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://www.example.org/PersonService/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" name="PersonService" targetNamespace="http://www.example.org/PersonService/"> <wsdl:types> <xsd:schema> <xsd:element name="personID" type="xsd:int"></xsd:element> <xsd:element name="person"> <xsd:complexType> <xsd:sequence> <xsd:element ref="personID"></xsd:element> <xsd:element name="name" type="xsd:string"></xsd:element> <xsd:element name="age" type="xsd:int"></xsd:element> <xsd:element name="gender"> <xsd:simpleType> <xsd:restriction base="xsd:string"> <xsd:enumeration value="male"></xsd:enumeration> <xsd:enumeration value="female"></xsd:enumeration> </xsd:restriction> </xsd:simpleType> </xsd:element> </xsd:sequence> </xsd:complexType> </xsd:element> <xsd:element name="personRequest"> <xsd:complexType> <xsd:sequence> <xsd:element ref="personID"></xsd:element> </xsd:sequence> </xsd:complexType> </xsd:element> <xsd:element name="personResponse"> <xsd:complexType> <xsd:sequence> <xsd:element ref="person"></xsd:element> </xsd:sequence> </xsd:complexType> </xsd:element> <xsd:element name="PersonFault"> <xsd:complexType> <xsd:sequence> <xsd:element name="error" type="xsd:string"></xsd:element> </xsd:sequence> </xsd:complexType> </xsd:element> </xsd:schema> </wsdl:types> <wsdl:message name="personRequest"> <wsdl:part name="personRequest" element="personRequest"></wsdl:part> </wsdl:message> <wsdl:message name="personResponse"> <wsdl:part name="personResponse" element="personResponse"></wsdl:part> </wsdl:message> <wsdl:message name="PersonFault"> <wsdl:part name="PersonFault" element="PersonFault"></wsdl:part> </wsdl:message> <wsdl:portType name="PersonServicePort"> <wsdl:operation name="getPerson"> <wsdl:input message="tns:personRequest"></wsdl:input> <wsdl:output message="tns:personResponse"></wsdl:output> <wsdl:fault name="PersonFault" message="tns:PersonFault"></wsdl:fault> </wsdl:operation> </wsdl:portType> <wsdl:binding name="PersonServicePortBinding" type="tns:PersonServicePort"> <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/> <wsdl:operation name="getPerson"> <soap:operation soapAction="getPerson"/> <wsdl:input name="personRequest"> <soap:body use="literal"/> </wsdl:input> <wsdl:output name="personResponse"> <soap:body use="literal"/> </wsdl:output> <wsdl:fault name="PersonFault"> <soap:fault name="PersonFault" use="literal"/> </wsdl:fault> </wsdl:operation> </wsdl:binding> <wsdl:service name="PersonService"> <wsdl:port name="PersonServicePort" binding="tns:PersonServicePortBinding"> <soap:address location="http://localhost:8080/WebService/PersonService"/> </wsdl:port> </wsdl:service> </wsdl:definitions>


i think there is some problem with the wsdl. but unable to find it out. can you please help me rancher.........

[Ivan Krizsan]

Hi!
When you try to create a project in soapUI, are there any error messages?
Were you able to successfully create a project with a sample request for the operation of your web service?
I tried to use your WSDL in soapUI and my answers to the above are "yes" and "no".
I'll give you a clue: There are some unnecessary parts in your <binding> element (including child elements).
Upon doubt, I suggest you to look at a WSDL that is known to be good and compare with your WSDL.
Best wishes!

[Avinash Ga]

Thanks Ivan...... yes , im also not able to generate a soap request from SoapUI. Thanks for your suggestion. i will try that.

Also ivan im really grateful for your study materials on the certification. Thats really great. im following the same with the one written by Mikalai for my certification. thanks again.

[Avinash Ga]

Hi Ivan,

Finally i resolved the issue . the problem was with my wsdl . the input/output section inside the porttype was not having name attribute. fixed the same .

here is my port type.

<wsdl:portType name="PersonServicePort"> <wsdl:operation name="getPerson"> <wsdl:input name="personRequest" message="tns:personRequest"></wsdl:input> <wsdl:output name="personResponse" message="tns:personResponse"></wsdl:output> <wsdl:fault name="PersonFault" message="tns:PersonFault"></wsdl:fault> </wsdl:operation> </wsdl:portType>

Thanks Again.......

[Avinash Ga]

This time im able to generate the sample request using soapui . but when i submit the request im getting the error

here is my updated (latest) wsdl :-


<?xml version="1.0" encoding="UTF-8"?> <wsdl:definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://www.example.org/PersonService/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" name="PersonService" targetNamespace="http://www.example.org/PersonService/"> <wsdl:types> <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://www.example.org/PersonService/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" elementFormDefault="qualified" targetNamespace="http://www.example.org/PersonService/"> <xsd:element name="personID" type="xsd:int"></xsd:element> <xsd:element name="person"> <xsd:complexType> <xsd:sequence> <xsd:element ref="tns:personID"></xsd:element> <xsd:element name="name" type="xsd:string"></xsd:element> <xsd:element name="age" type="xsd:int"></xsd:element> <xsd:element name="gender"> <xsd:simpleType> <xsd:restriction base="xsd:string"> <xsd:enumeration value="male"></xsd:enumeration> <xsd:enumeration value="female"></xsd:enumeration> </xsd:restriction> </xsd:simpleType> </xsd:element> </xsd:sequence> </xsd:complexType> </xsd:element> <xsd:element name="personRequest"> <xsd:complexType> <xsd:sequence> <xsd:element ref="tns:personID"></xsd:element> </xsd:sequence> </xsd:complexType> </xsd:element> <xsd:element name="personResponse"> <xsd:complexType> <xsd:sequence> <xsd:element ref="tns:person"></xsd:element> </xsd:sequence> </xsd:complexType> </xsd:element> <xsd:element name="PersonFault"> <xsd:complexType> <xsd:sequence> <xsd:element name="error" type="xsd:string"></xsd:element> </xsd:sequence> </xsd:complexType> </xsd:element> </xsd:schema> </wsdl:types> <wsdl:message name="personRequest"> <wsdl:part name="personRequest" element="tns:personRequest"></wsdl:part> </wsdl:message> <wsdl:message name="personResponse"> <wsdl:part name="personResponse" element="tns:personResponse"></wsdl:part> </wsdl:message> <wsdl:message name="PersonFault"> <wsdl:part name="PersonFault" element="tns:PersonFault"></wsdl:part> </wsdl:message> <wsdl:portType name="PersonServicePort"> <wsdl:operation name="getPerson"> <wsdl:input name="personRequest" message="tns:personRequest"></wsdl:input> <wsdl:output name="personResponse" message="tns:personResponse"></wsdl:output> <wsdl:fault name="PersonFault" message="tns:PersonFault"></wsdl:fault> </wsdl:operation> </wsdl:portType> <wsdl:binding name="PersonServicePortBinding" type="tns:PersonServicePort"> <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/> <wsdl:operation name="getPerson"> <soap:operation soapAction="getPerson"/> <wsdl:input name="personRequest"> <soap:body use="literal"/> </wsdl:input> <wsdl:output name="personResponse"> <soap:body use="literal"/> </wsdl:output> <wsdl:fault name="PersonFault"> <soap:fault name="PersonFault" use="literal"/> </wsdl:fault> </wsdl:operation> </wsdl:binding> <wsdl:service name="PersonService"> <wsdl:port name="PersonServicePort" binding="tns:PersonServicePortBinding"> <soap:address location="http://localhost:8080/WebService/PersonService"/> </wsdl:port> </wsdl:service> </wsdl:definitions>


also here is my soap request :-

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ext="http://www.example.org/PersonService/"> <soapenv:Header/> <soapenv:Body> <ext:personRequest> <ext:personID>1</ext:personID> </ext:personRequest> </soapenv:Body> </soapenv:Envelope>

and the soap response is :-

<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:Server</faultcode> <faultstring>unexpected XML tag. expected: {http://www.example.org/PersonService/}getPerson but found: {http://www.example.org/PersonService/}personRequest</faultstring> </S:Fault> </S:Body> </S:Envelope>




can anyone help?

Thanks in advance

[James Boswell]

Your SOAP request is missing the element getPerson which wraps a personRequest.

[Avinash Ga]

Thanks James. i will try that.

[Avinash Ga]

Hi James,

in the wsdl, input message is of the type personRequest and im passing the same from my soap ui. can you please let me know the solution?

Thanks

[Avinash Ga]

also if i use this soap message.

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:per="http://www.example.org/PersonService/"> <soapenv:Header/> <soapenv:Body> <per:getPerson> <per:personRequest> <per:personID>1</per:personID> </per:personRequest> </per:getPerson> </soapenv:Body> </soapenv:Envelope>


im getting.

<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.example.org/PersonService/}getPerson</faultstring> </S:Fault> </S:Body> </S:Envelope>

one more thing..... im a newbie to jax-ws.

[James Boswell]

Avinash

I think this is progressing. Can you show the java code for your web methods please?

[Avinash Ga]

Hi James,

Here is my java code.....

Endpoint Interface.

@WebService(name="PersonServicePort", targetNamespace="http://www.example.org/PersonService/")
public interface PersonServicePort {
	@WebMethod(operationName="getPerson")
	public @WebResult(name="personResponse") PersonResponse getPerson(@WebParam PersonRequest personRequest) 
			throws PersonFault_Exception;
	
}

and here is the service....

@WebService(name = "PersonService", serviceName="PersonService", endpointInterface = "service.PersonServicePort", targetNamespace="http://www.example.org/PersonService/", wsdlLocation="WEB-INF/wsdl/PersonService.wsdl")
public class PersonService implements PersonServicePort {

	@WebMethod(operationName="getPerson")
	public @WebResult(name="personResponse") PersonResponse getPerson(@WebParam(name="personRequest", partName="personRequest") PersonRequest personRequest)
			throws PersonFault_Exception {
		PersonResponse personResponse = new PersonResponse();
		
		Person p1 = new Person();
		p1.setAge(1);
		p1.setGender("male");
		p1.setName("p1");
		p1.setPersonID(1);
		
		personResponse.setPerson(p1);
		return personResponse;
	}

}

one weird thing.....

i published the same web service using EndPoint api and for the request

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:per="http://www.example.org/PersonService/"> <soapenv:Header/> <soapenv:Body> <per:personRequest> <per:personID>2</per:personID> </per:personRequest> </soapenv:Body> </soapenv:Envelope>


im getting the response.
<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"> <S:Body> <ns2:getPersonResponse xmlns:ns2="http://www.example.org/PersonService/"> <personResponse> <person> <age>1</age> <gender>male</gender> <name>p1</name> <personID>1</personID> </person> </personResponse> </ns2:getPersonResponse> </S:Body> </S:Envelope>

its kinda working..... but i dont know why this tag in the response (<ns2:getPersonResponse xmlns:ns2="http://www.example.org/PersonService/">).
atleast it is working if i use EndPoint api to publish.

but the same thing if i deploy in GlassFish server im getting
<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:Server</faultcode> <faultstring>unexpected XML tag. expected: {http://www.example.org/PersonService/}getPerson but found: {http://www.example.org/PersonService/}personRequest</faultstring> </S:Fault> </S:Body> </S:Envelope>

as a response.

attached is the whole of my (silly) project with ant script. just "ant build" will generate a deployable war. please change the extension of the file to *.zip


Thanks Again

[Sergio Eduardo D Oliveira]

Hi there!

It's been quite a long time since this question has been asked and it still remains without a straightforward solution. Nonetheless, I'm dealing with the very same error you were getting.

The whole hassle is about the attribute "ref". In your code, it's represented in the snippet <xsd:element ref="tns:personID"></xsd:element>. by using this attribute in WSDL, the JAX-WS generates the class with its aforementioned attribute annotated with

@XmlElement(namespace = "http://namespaceexample")

, however, when you try to send this object to the endpoint you get the error

Unmarshalling Error: unexpected element (uri:"....", local:"...."). Expected elements are...

.

First, I'm using CXF to generate the classes, so I tried to upgrade it to a newer version and check if the class attribute was generated correctly (without the annotation). I also tried to use JAX-WS to generate the classes but it turns out all approaches were adding the same annotation config to the field.

After some time analyzing the WSDL which was supposed to generate the domain classes correctly, I realized that if I change the "ref" attribute to "type" and add a "name" attribute with the same property name, the class file got generated correctly.
So in your case, you would have to change the structure of the person element in your WSDL to the following snippet:

<xsd:element name="person">            <xsd:complexType>                <xsd:sequence>                    <!-- change it here: --><xsd:element name="personID" type="xsd:int"></xsd:element>                    <xsd:element name="name" type="xsd:string"></xsd:element>                    <xsd:element name="age" type="xsd:int"></xsd:element>                    <xsd:element name="gender">                        <xsd:simpleType>                            <xsd:restriction base="xsd:string">                                <xsd:enumeration value="male"></xsd:enumeration>                                <xsd:enumeration value="female"></xsd:enumeration>                            </xsd:restriction>                        </xsd:simpleType>                    </xsd:element>                </xsd:sequence>            </xsd:complexType>        </xsd:element>

I don't know why it gets generated this way and why the same endpoint does not accept the soap message with the namespace in the element, but I know that if you remove the namespace from the element <per:personID>2</per:personID>while you're sending your SOAP message it will work just fine.

It also works if you remove the annotation

@XmlElement(namespace = ".....")

from the troublesome attribute, but this annotation will be put back again whenever you build your web service classes from the scratch WSDL, so you'd better change the local WSDL either way.

I'm using a third party web service, which I have no idea how it was developed.