Databases
StackOverflow2013
Postsdbo
POIncompatible Axis 1 client with Axis 2 Web Service
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POIncompatible Axis 1 client with Axis 2 Web Service
    primarykey
    data
    text
    <p>I have an Axis 1 web service with an Axis 1 client. Everything is working quite well, and the data I'm getting from the web service is correct. Now, there's a requirement to move the web service to use Axis 2, I'm having problems to get data on the Axis 1 client. I have used SOAPUI to see the format of the response that I'm getting.</p> <p>With the Axis 1 web service, the response was as follows:</p> <pre><code>&lt;soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"&gt; &lt;soapenv:Body&gt; &lt;getInventoryResponse xmlns="http://webservices.com"&gt; &lt;getInventory&gt; &lt;errorCode&gt;10071&lt;/errorCode&gt; &lt;inventory xsi:nil="true"/&gt; &lt;/getLastInventoryCountReturn&gt; &lt;/getInventoryResponse&gt; &lt;/soapenv:Body&gt; &lt;/soapenv:Envelope&gt; </code></pre> <p>With the Axis 2 web service, the response is as follows:</p> <pre><code>&lt;soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"&gt; &lt;soapenv:Body&gt; &lt;ns:getInventoryResponse xmlns:ns="http://webservices.com"&gt; &lt;ns:return xsi:type="ax21:Inventory" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ax21="http://model.com/xsd"&gt; &lt;ax21:errorCode&gt;10071&lt;/ax21:errorCode&gt; &lt;ax21:inventory xsi:nil="true"/&gt; &lt;/ns:return&gt; &lt;/ns:getInventoryResponse&gt; &lt;/soapenv:Body&gt; &lt;/soapenv:Envelope&gt; </code></pre> <p>As you can see, the element called "errorCode" has a value of 10071. I'm receiving the errorCode value correctly on the client from both web services. But I have a complex type called "Inventory" that I receive as part of the response (It doesn't appear in the responses I have included above 'cause it will take me some time to populate the appropriate data on the web service). The InventoryItem contains fields of different data types (String, Calendar). What I have noticed is that the response from the Axis 2 web service contains the <code>&lt;axs21&gt;</code> xml tag whereas in the Axis 1 web service, it's not there. So I'm assuming that I have a parsing problem on the client side with the response coming from the Axis 2 web service.</p> <p>Does anyone know how can I solve this?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USMouhammed Soueidane
    1. USMouhammed Soueidane
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COWhat are the incompatibilities you see with the Axis2 generated wsdl? Axis2 generates doc/lit type wsdl by default. This should work with any soap frame work.
      singulars
      1. POIncompatible Axis 1 client with Axis 2 Web Service
      1. USAmila Suriarachchi
    2. COI have edited my post to better describe the problem. Please check it and let me know what do you think.
      singulars
      1. POIncompatible Axis 1 client with Axis 2 Web Service
      1. USMouhammed Soueidane
 

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