A problem parsing the response envelope.

[Krzysiek Hycnar]

Hi all,

I've got a weird problem trying to consume a Web Service published by a third party company. The problem occures when the client is trying to parse the response envelope. In case of JAXWS based client instead of a non blank string, null value is returned, and if the JAXRPC client is used I get the following exception:

    
Exception in thread "main" java.rmi.RemoteException: Runtime exception; nested exception is: 
unexpected element name: expected=reference, actual={urn:NetBanxDirectDebit}reference
at com.sun.xml.rpc.client.StreamingSender._handleRuntimeExceptionInSend(StreamingSender.java:331)
at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:313)
at ptv.payments.netbanx.directdebit.jaxrpc.NetBanxDirectDebitPortType_Stub.create_schedule(NetBanxDirectDebitPortType_Stub.java:354)
at ptv.payments.netbanx.directdebit.jaxrpc.Client.main(Client.java:14)
Caused by: unexpected element name: expected=reference, actual={urn:NetBanxDirectDebit}reference
at ptv.payments.netbanx.directdebit.jaxrpc.NetBanxDirectDebitPortType_create_schedule_ResponseStruct_LiteralSerializer.doDeserialize(NetBanxDirectDebitPortType_create_schedule_ResponseStruct_LiteralSerializer.java:57)
at com.sun.xml.rpc.encoding.literal.LiteralObjectSerializerBase.internalDeserialize(LiteralObjectSerializerBase.java:216)
at com.sun.xml.rpc.encoding.literal.LiteralObjectSerializerBase.deserialize(LiteralObjectSerializerBase.java:124)
at ptv.payments.netbanx.directdebit.jaxrpc.NetBanxDirectDebitPortType_Stub._deserialize_create_schedule(NetBanxDirectDebitPortType_Stub.java:1337)
at ptv.payments.netbanx.directdebit.jaxrpc.NetBanxDirectDebitPortType_Stub._readFirstBodyElement(NetBanxDirectDebitPortType_Stub.java:1213)
at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:228)
... 2 more

I managed to fix the problem in the JAXRPC client by manually editing one of the generated classes - I had to replace the originally generated part...

 ns1_reference_QNAME = new QName("", "reference"); 

with

 ns1_reference_QNAME = new QName("urn:NetBanxDirectDebit", "reference");

Also, as you can see below in the sample response envelope returned by the service the create_scheduleResponse message is defined as: <create_scheduleResponse xmlns="urn:NetBanxDirectDebit"> and that suggests that the above exception is raised because the parser is expecting the response element not to be placed within the urn:NetBanxDirectDebit namespace (and obviously creating the QName manually with the namespace specified fixed the problem).

The wsdl looks like follows (some parts of it have been cut):

   
<?xml version="1.0"?>
<definitions name="NetBanxDirectDebit" targetNamespace="urn:NetBanxDirectDebit" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:nbx="urn:NetBanxDirectDebit">
 
  <message name="create_scheduleRequest">
    <part name='username' type='xsd:string'/>
    <part name='password' type='xsd:string'/>
    <part name='values' type='xsd:string'/>
  </message>
  <message name="create_scheduleResponse">
    <part name='reference' type='xsd:string'/>
  </message>
 
  <portType name="NetBanxDirectDebitPortType">
    <operation name="create_schedule">
      <input message="nbx:create_scheduleRequest"/>
      <output message="nbx:create_scheduleResponse"/>
    </operation>
  </portType>
 
  <binding name="NetBanxDirectDebitBinding" type="nbx:NetBanxDirectDebitPortType">
    <soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
    <operation name="create_schedule">
      <soap  :-o	  peration soapAction="urn:NetBanxDirectDebit#create_schedule"/>
      <input><soap:body use="literal" namespace="urn:NetBanxDirectDebit"/></input>
      <output><soap:body use="literal" namespace="urn:NetBanxDirectDebit"/></output>
    </operation>
  </binding>
  <service name="NetBanxDirectDebitService">
    <port binding="nbx:NetBanxDirectDebitBinding" name="NetBanxDirectDebit">
      <soap:address location="http://localhost:9000/cgi-bin/soap_rpc"/>
    </port>
  </service>
</definitions>

Sample request envelope:

<?xml version="1.0" ?>
<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<S:Body>
<ns2:create_schedule xmlns:ns2="urn:NetBanxDirectDebit">
<username>username</username>
<password>password</password>
<values>2500,2000,2000</values>
</ns2:create_schedule>
</S:Body>
</S:Envelope>

and a sample response envelope:

   
<?xml version="1.0" encoding="UTF-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
soap:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<create_scheduleResponse xmlns="urn:NetBanxDirectDebit">
<reference xsi:type="xsd:string">
54X8UYCTLBRK9CY97O
</reference>
</create_scheduleResponse>
</soap:Body>
</soap:Envelope>

I believe manual editing of the generated stubs is not the way to go, at the same time I admit, I'm a newbie when it commes to Web Services, so my requestion is:

What can be said having the above data? Is there any specific way I need to generate the client stubs, or the wsdl does not quite describe the service itself?

Thank you in advance for any help!
Krzysztof
[ December 08, 2008: Message edited by: Krzysiek Hycnar ]