org.apache.asix2.saaj.SOAPConnectionImpl does not handle MimeHeaders(WebSphere Application Server Community Edition 2.1.1.6)

Technote (troubleshooting)


Problem(Abstract)

MimeHeaders couldn't be past dowm from SOAPMessage to the ServiceClient, So all the SOAPMessages would be with empty SOAPAction as "". Since the Authorization HTTP Header cann't be set, it is not possible to properly secure SAAJ services using HTTP authentication. Because the WSA-Addressing Action value isn't the same as the SOAPAction header, WS-Security doesn't work, either.

Resolving the problem

To fix this issue, please follow the instruction.

1. Download the patch.SOAPActionMIMEHeader.zipSOAPActionMIMEHeader.zip

2. Unzip the attached file into the WebSphere Application Server Community Edition installation directory, and ensure the files listed in the zip file to replace the ones in the server installation directory.

3. Start the server, for example,

<WAS_CE_HOME>\bin\startup.bat

<WAS_CE_HOME>/bin/startup.sh


Related information

AXIS2-1014

Rate this page:

(0 users)Average rating

Document information


More support for:

WebSphere Application Server Community Edition
AxisWebServices

Software version:

2.1.1.6

Operating system(s):

AIX, Linux, Solaris, Windows

Software edition:

Elite, Enhanced, Entry

Reference #:

1621280

Modified date:

2012-12-28

Translate my page

Machine Translation

Content navigation