PI48668: ADD A JVM PROPERTY TO ENABLE THE "ORG.APACHE.AXIOM.OM.OMFORMAT.U SE.CTEBASE64.FORNONTEXTUALATTACHMENTS" FORMAT PROPERTY.

8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

APAR status

• Closed as new function.

Error description

• Add a JVM property to enable the
  "org.apache.axiom.om.OMFormat.use.cteBase64.forNonTextualAttachm
  ents" format property.
  
  The
  "org.apache.axiom.om.OMFormat.use.cteBase64.forNonTextualAttachm
  ents" is an axiom property, used to set the "non textual"
  attachments "content-transfer-encoding" type to "base64"
  
  The value of this property is a Boolean. A missing value
  indicates the default action, which is Boolean.FALSE. If
  Boolean.TRUE, attachments that are "non textual" are written
  out with a "content-transfer-encoding" type of "base64".
  
  Example:
  An attachment with a content-type of "image/gif" is a
  non-textual attachment.
  An attachment with a content-type of "application/soap+xml" is
  an textual attachment.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  IBM WebSphere Application Server users of   *
  *                  JAX-WS web services.                        *
  ****************************************************************
  * PROBLEM DESCRIPTION: "Content-Transfer-Encoding" type of a   *
  *                      non-textual attachment is always set    *
  *                      to "binary" even it is set to           *
  *                      "base64" in the application source      *
  *                      code.                                   *
  ****************************************************************
  * RECOMMENDATION:  Install a fix pack containing this APAR.    *
  ****************************************************************
  Non-textual attachment "Content-Transfer-Encoding" type is
  "binary" even it is set to "base64" in the application source
  code, as follow:
  SOAPMessage message = arg0.getMessage();
  AttachmentPart ap = message.createAttachmentPart();
  ap.setMimeHeader("Content-Transfer-Encoding", "base64");
  

Problem conclusion

• There is a switch in the axiom code to set "base64" in
  "Content-Transfer-Encoding" for attachments. Added a JVM
  property
  "com.ibm.ws.websvcs.transport.http.isAttachmentBase64Format"
  to enable this axiom format property.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.5.5.9.  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 is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WEBSPHERE APP S

• Fixed component ID

  5724J0800

Applicable component levels

• R850 PSY

     UP