Upgrading from Axis2/Java 1.4.1 to 1.5.1 (missing SOAP header)

View: New views
2 Messages — Rating Filter:   Alert me  

Upgrading from Axis2/Java 1.4.1 to 1.5.1 (missing SOAP header)

by SGE0 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi,

we have been upgrading from 1.4.1 to 1.5.1

Our services are working but we still do not feel comfortable with it:

When we look in the SOAPMonitor (server site) we could find our request as following in Axis2/Java 1.4.1 :

<?xml version='1.0' encoding='utf-8'?>
 <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
  <soapenv:Header xmlns:wsa="http://www.w3.org/2005/08/addressing">
    <wsa:MessageID>urn:uuid:DD04F12C3872B6578F1234360243487</wsa:MessageID>
    <wsa:Action>urn:upload</wsa:Action>
  </soapenv:Header>
  <soapenv:Body>
    <ns1:upload xmlns:ns1="http://services.test.be">
      <ns1:pdfdocument>JVBGCg==</ns1:pdfdocument>
      <ns1:documentURI>Example.pdf</ns1:documentURI>
    </ns1:upload>
  </soapenv:Body>
</soapenv:Envelope>

With version 1.5.1, the request is:

<?xml version='1.0' encoding='utf-8'?>
<soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
  <soapenv:Body>
    <ns1:upload xmlns:ns1="http://services.test.be">
      <ns1:pdfdocument>JVBERi0T0YN</ns1:pdfdocument>
      <ns1:documentURI>Corp.pdf</ns1:documentURI>
    </ns1:upload>
  </soapenv:Body>
</soapenv:Envelope>


The SOAP Header is missing (although the service works as expected).

Is this correct ? Has this to do with the different soapenv version used ?

Can someone explain if this is the correct behavior ?

Regards,

S.

Re: Upgrading from Axis2/Java 1.4.1 to 1.5.1 (missing SOAP header)

by SGE0 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi All,

this was solved. The problem was that we did not properly update the client (meaning a mix of 1.4.1. jars and 1.5.1. jars).

We restarted and now it works...

S.
SGE0 wrote:
Hi,

we have been upgrading from 1.4.1 to 1.5.1

Our services are working but we still do not feel comfortable with it:

When we look in the SOAPMonitor (server site) we could find our request as following in Axis2/Java 1.4.1 :

<?xml version='1.0' encoding='utf-8'?>
 <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
  <soapenv:Header xmlns:wsa="http://www.w3.org/2005/08/addressing">
    <wsa:MessageID>urn:uuid:DD04F12C3872B6578F1234360243487</wsa:MessageID>
    <wsa:Action>urn:upload</wsa:Action>
  </soapenv:Header>
  <soapenv:Body>
    <ns1:upload xmlns:ns1="http://services.test.be">
      <ns1:pdfdocument>JVBGCg==</ns1:pdfdocument>
      <ns1:documentURI>Example.pdf</ns1:documentURI>
    </ns1:upload>
  </soapenv:Body>
</soapenv:Envelope>

With version 1.5.1, the request is:

<?xml version='1.0' encoding='utf-8'?>
<soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
  <soapenv:Body>
    <ns1:upload xmlns:ns1="http://services.test.be">
      <ns1:pdfdocument>JVBERi0T0YN</ns1:pdfdocument>
      <ns1:documentURI>Corp.pdf</ns1:documentURI>
    </ns1:upload>
  </soapenv:Body>
</soapenv:Envelope>


The SOAP Header is missing (although the service works as expected).

Is this correct ? Has this to do with the different soapenv version used ?

Can someone explain if this is the correct behavior ?

Regards,

S.