Pascal Knüppel created AXIS2-5741:
-------------------------------------

             Summary: clients cannot resolve service reponse
                 Key: AXIS2-5741
                 URL: https://issues.apache.org/jira/browse/AXIS2-5741
             Project: Axis2
          Issue Type: Bug
          Components: client-api, jaxws
    Affects Versions: 1.7.0
            Reporter: Pascal Knüppel
             Fix For: 1.5.1


We have developed an axis2 service some years ago but had some security issues 
with it. Therefore we now patched to version 1.7.0. We got 2 test clients, one 
JAX-WS-client and an axis2-client. Both are working perfectly with the old 
version. But when sending requests to the axis2 service in version 1.7.0 the 
clients cannot resolve the response, though the service is answering correctly. 
What can be the reason of this? JAX-WS-client is returning null and 
axis2-client is throwing an exception of unknown elemtn eventhough the 
mentioned element is absolutely correct. I watched the traffic via fiddler to 
find differences in the reponses of the old version client and the new version 
client. But the differences are minor and do not justify that the clients 
cannot resolve it. I never had this kind of problem with webservices except for 
this axis2-version.

here is the service-response from the old service version 1.5.1 that the 
clients accept correctly

POST ...
SOAPAction: "ladeRzVersion"
Accept: text/xml, multipart/related, text/html, image/gif, image/jpeg, *; q=.2, 
*/*; q=.2
Content-Type: text/xml;charset="utf-8"
User-Agent: JAX-WS RI 2.1.4-b01-
Host: ...
Connection: keep-alive
Transfer-Encoding: chunked

6e
<?xml version='1.0' encoding='UTF-8'?><S:Envelope 
xmlns:S="http://schemas.xmlsoap.org/soap/envelope/";><S:Body>
2d3
<ns2:ladeRzVersion 
xmlns:ns2="http://fiverx.de/spec/abrechnungsservice/types";><rzeParamLadeVersion>&lt;?xml
 version="1.0" encoding="utf-8"?&gt;
&lt;rzeParamLadeVersion xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; 
xmlns:xsd="http://www.w3.org/2001/XMLSchema"; 
xmlns="http://fiverx.de/spec/abrechnungsservice"&gt;
        &lt;sendHeader&gt;
                &lt;rzKdNr&gt;12345&lt;/rzKdNr&gt;
                &lt;avsSw&gt;
                        &lt;hrst&gt;PHARMATECHNIK&lt;/hrst&gt;
                        &lt;nm&gt;IXOS&lt;/nm&gt;
                        &lt;vs&gt;1.0&lt;/vs&gt;
                &lt;/avsSw&gt;
                &lt;apoIk&gt;301234561&lt;/apoIk&gt;
                &lt;test&gt;true&lt;/test&gt;
                &lt;pw&gt;123456&lt;/pw&gt;
        &lt;/sendHeader&gt;
&lt;/rzeParamLadeVersion&gt;</rzeParamLadeVersion></ns2:ladeRzVersion></S:Body></S:Envelope>
0



And here the new service (verson 1.7.0) response that the clients do not accept.

POST ...
SOAPAction: ""
Accept: text/xml, multipart/related, text/html, image/gif, image/jpeg, *; q=.2, 
*/*; q=.2
Content-Type: text/xml;charset="utf-8"
User-Agent: JAX-WS RI 2.1.4-b01-
Host:...
Connection: keep-alive
Transfer-Encoding: chunked

6e
<?xml version='1.0' encoding='UTF-8'?><S:Envelope 
xmlns:S="http://schemas.xmlsoap.org/soap/envelope/";><S:Body>
7a
<ns2:ladeRzVersion 
xmlns:ns2="http://fiverx.de/spec/abrechnungsservice/types";><rzeParamLadeVersion>&lt;?xml
 version="1.0" 
7a
encoding="utf-8"?&gt;
&lt;rzeParamLadeVersion xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; 
xmlns:xsd="http://www.
7a
w3.org/2001/XMLSchema" xmlns="http://fiverx.de/spec/abrechnungsservice"&gt;
        &lt;sendHeader&gt;
                &lt;rzKdNr&gt;12345&lt;/
7a
rzKdNr&gt;
                &lt;avsSw&gt;
                        &lt;hrst&gt;PHARMATECHNIK&lt;/hrst&gt;
                        &lt;nm&gt;IXOS&lt;/nm&gt;
                        &lt;vs&gt;1.0&lt;/vs&
7a
gt;
                &lt;/avsSw&gt;
                &lt;apoIk&gt;301234561&lt;/apoIk&gt;
                &lt;test&gt;true&lt;/test&gt;
                &lt;pw&gt;123456&lt;/pw&gt;

71
        &lt;/sendHeader&gt;
&lt;/rzeParamLadeVersion&gt;</rzeParamLadeVersion></ns2:ladeRzVersion></S:Body></S:Envelope>
0




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to