Fix (APAR):  WAS_WebServices-WSIF_05-01-2003_5.0.1-5.0.0_cumulative_Fix

Status:  Fix

Release:  5.0.1,5.0.0

Operating System:  All

Supersedes Fixes:  WAS_WebServices-WSIF_04-17-2003_5.0.1-5.0.0_cumulative_Fix



CMVC Defect:  

Byte size of APAR:  425859

Date: 2003-05-13

Abstract:  Cumulative WSIF interim fix for WAS Enterprise

Description/symptom of problem:  Cumulative Web Services Invocation Framework (WSIF) interim fix
          d151011   cloning null pointers not handled efficiently
          d151796   Elements not supported in XSD types
          d152193   WSIF JMS Provider overwrites JMSReplyTo property set by DF
          d152204   no client transport"JMS" error when axis tech preview installed
          d152311   Excessive WSDLException: faultCode=CONFIGURATION_ERROR: tracing
          d152648   setting JMSType header gives MQJMS1058 Invalid msg property
          d152744   Cannot execute char argument method
          d152861   Can't WSDL with JMS extension without causing JNDI lookups
          d152972   Java and EJB provider need to support mulipart output messages.
          d153304   Minor fixes to translated files
          d153392   ClassNotFound exceptions from WSIFUtils.getFormatHandler()
          d153567   Need to put wsif jca jar file into WAS Base  for JCA atomic sup
          d153683.1 MsgDef of WSIFDefaultmessage is not set
          d154232   WSIFProviders registered multiple times causing WSIF0006W
          d154291   WSIFPort_JMS doesn't close its connections.
          d154297   JMSExpiration property incorrectly supported as Integer
          d154658   Null parts cause null pointer exception in Java provider
          d154672   SOAP Literal encoding serializer registration
          d154825   Unable to call process with char[] argument
          d154862   Infinite loop can be encountered when reading wsdl files
          d154871   Java and EJB provider do not handle elements in the bindings
          d155052   WSIFException msgs in English, DBCS codepage corrupts msg
          d155303   WSIFException invoking a method taking a complex type,ret array
          d155383   SOAPHTTPConnection not serializable exception
          d155429   WSIFUtils does not remove invalid java character
          d155459   J2C provider: Add serial version UID
          d155493   IE: TVT:JP-Fatal error when running CICS sample
          d155584   SOAP Literal encoding serializer registration
          d157008   SOAP headers aren't put into the context message on response
          d157014   Getting a receive timeout using synchronous JMS provider
          d157014   Receive timeout using synchronous call to JMS provider
          d157021   WSIFUtils.getExtensionRegistry() support required
          d157290   JMS Message incorrectly uses the message namespace to compute to compute the part QName
          d158775   getCharPart gets a string not a char
          d160051   URI to package name: underscore should be removed
          d160459   Expose JMS header properties setting API
          d162980   Better setting of fields in JMSFormatter
          d164858*  JMS header properties API should remove properties from the source message

Fixes with * have been added since WAS_WebServices-WSIF_04-17-2003_5.0.1-5.0.0_cumulative_Fix




Directions to apply fix:  

NOTE:  YOU MUST FIRST DOWNLOAD THE UPDATE INSTALLER TOOL IN ORDER TO INSTALL A FIX.
       The Fix Installer can be downloaded from the following link:
       http://www-3.ibm.com/software/webservers/appserv/support/index.html

1) Create temporary "fix" directory to store the jar file:
             UNIX: /tmp/WebSphere/fix
          Windows: c:\temp\WebSphere\fix

2) Copy jar file to the directory

3) Shutdown WebSphere

4) Follow the Fix installation instructions that are packaged with the Fix Installer on how to install the Fix.

5) Restart WebSphere

6) The temp directory may be removed.



Directions to remove fix:  
NOTE:  FIXES MUST BE REMOVED IN THE ORDER THEY WERE APPLIED.  DO NOT REMOVE A FIX UNLESS
     ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED.  YOU MAY REAPPLY ANY REMOVED FIX.

Example:  If your system has fix1, fix2, and fix3 applied in that order and fix2 is to be
          removed, fix3 must be removed first, fix2 removed, and fix3 re-applied.


1) Shutdown WebSphere

2) Follow the instructions that are packaged with the Fix Installer on how to uninstall the Fix.

3) Restart WebSphere



Directions to re-apply fix:  
1) Shutdown WebSphere

2) Follow the Fix instructions that are packaged with the Fix Installer on how to uninstall and reinstall the Fix.

3) Restart WebSphere





Additional Information: