PM19608: JAVAX.XML.SOAP.MESSAGEFACTORY.NEWINSTANCE() MIGHT RETURN WRONG OBJECT

6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server

APAR status

• Closed as program error.

Error description

• The way WebSphere Application Server creates a new
  MessageFactory or SOAPFactory instance does not conform to the
  Java specification, in terms of the lookup procedure order
  to determine the MessageFactory or SOAPFactory implementation
  class to load.
  
  For example, there is no effect if setting the
  "javax.xml.soap.MessageFactory" system property.
  
  Instead of returning an object of the class defined in the
  system property setting, the WebSphere Application Server
  runtime always uses the SAAJMetaFactory instance to locate the
  MessageFactory implementation class.  Thus, an object of the
  wrong class might be returned.
  
  The same is true for javax.xml.soap.SOAPFactory.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  IBM WebSphere Application Server V6.1 users *
  *                  of SAAJ                                     *
  ****************************************************************
  * PROBLEM DESCRIPTION: MessageFactory and SOAPFactory          *
  *                      newInstance methods might return        *
  *                      instance of wrong class.                *
  ****************************************************************
  * RECOMMENDATION:  Install a fixpack containing this APAR.     *
  ****************************************************************
  The way WebSphere Application Server creates a new
  javax.xml.soap.MessageFactory or javax.xml.soap.SOAPFactory
  instance does not conform to the SAAJ 1.3 Specification,
  in terms of the lookup procedure in order to determine the
  MessageFactory or SOAPFactory implementation class to load.
  
  For example, there is no effect if the
  "javax.xml.soap.MessageFactory" system property is set.
  
  Instead of providing an object of the class defined in the
  system property setting, the WebSphere Application Server
  runtime always uses the javax.xml.soap.SAAJMetaFactory instance
  to locate the MessageFactory implementation class.  Thus, an
  object of the wrong class might be returned.
  
  The same is true for javax.xml.soap.SOAPFactory.
  

Problem conclusion

• The algorithm for creating a new MessageFactory or SOAPFactory
  did not follow the specification in all cases.  In particular,
  the algorithm was always deferring to the SAAJMetaFactory even
  when a system property was present.  The algorithm has been
  changed to match the specification.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 6.1.0.37.  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

• R61A PSY

     UP

• R61H PSY

     UP

• R61I PSY

     UP

• R61P PSY

     UP

• R61S PSY

     UP

• R61W PSY

     UP

• R61Z PSY

     UP