APAR status
Closed as program error.
Error description
Lack of namespace in soap message causes failure in ibm_soap library when used with Internet Explorer. Having an issue with the ibm_soap dojo library included with the Feature Pack for Web2.0. It seems that the library cannot handle SOAP messages because of limitations in Microsoft Internet Explorer. Please note the following excerpt from ibm_soap/io/ws.js (line 57): if(dojo.isIE){ //IE does bad things, we have to remove namespaces. :-( namespace = null; nodename = nodename.substring(nodename.indexOf(":") + 1, nodename.length); return xDocument.createElement(nodename); } else { if(namespace){ return xDocument.createElementNS (namespace,nodename); }else{ return xDocument.createElement(nodename); } } The SOAP message dies because the <body> tag does not contain a namespace. A namespace can be manually added with the following code in ibm_soap/rpc/SoapService.js (line 39): //IE has a problem with some XML formats, have to work around //by modifying the return a bit. if(dojo.isIE){ bindInfo.postData = bindInfo.postData.xml; bindInfo.postData = bindInfo.postData.replace("<Body>", "<soapenv:Body>"); bindInfo.postData = bindInfo.postData.replace("</Body>", "</soapenv:Body>"); bindInfo.handleAs = "text"; }
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server Feature Pack for Web 2.0 and Mobile * * using the Soap Sample or ibm_soap dojo * * extension. * **************************************************************** * PROBLEM DESCRIPTION: Lack of namespace in a SOAP message * * causes a display failure in ibm_soap * * with Microsoft Internet Explorer. * **************************************************************** * RECOMMENDATION: * **************************************************************** Lack of namespace in a soap message causes a display failure in ibm_soap with Microsoft Internet Explorer. This problem will show a failure to process a SOAP message.
Problem conclusion
The ibm_soap and SoapSample code has been changed to avoid this failure The fix for this APAR is currently targeted for inclusion in Web 2.0 and Mobile FeP Fixpack 1.1.0.2. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PM60131
Reported component name
WAS WEB 2.0 FEA
Reported component ID
5724J0852
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-03-09
Closed date
2012-05-02
Last modified date
2012-05-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WAS WEB 2.0 FEA
Fixed component ID
5724J0852
Applicable component levels
R700 PSY
UP
R800 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
28 October 2021