PM25126: The message edited by a JAX-WS outbound client handler disappears if one of the JAX-WS handlers returns false.

7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

APAR status

• Closed as program error.

Error description

• Background:
  All JAX-WS handlers have a handleMessage method which you
  may use to query and change the XML message.
  If a JAX-WS handleMessage method returns false, the handler
  chain is reversed.
  
  For example, if a JAX-WS client outbound handler returns false
  the following occurs:
  A) The handler chain is reversed.
  B) The outbound message becomes the inbound message.
  C) The handlers that were previously called for outbound
  processing are called for inbound processing.
  D) Flow of control returns to the customer's JAX-WS
  BindingProvider (Dispatch or Proxy)
  
  
  Problem:
  In some cases, the (B) processing fails.  The outbound message
  is lost and a different message is used for the inbound
  processing.   The result is unexpected behavior when the flow
  of control returns to the customer's JAX-WS BindingProvider (D).
  
  Important Note:
  Most customer handlers will not return false.  This scenario
  is most common if you are writing a test application to
  simulate a web service invocation.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  IBM WebSphere Application Server V7.0 users *
  *                  of JAX-WS handlers                          *
  ****************************************************************
  * PROBLEM DESCRIPTION: The message edited by a JAX-WS          *
  *                      outbound client handler disappears if   *
  *                      one of the JAX-WS handlers returns      *
  *                      false.                                  *
  ****************************************************************
  * RECOMMENDATION:  Install an fix pack containing this APAR    *
  ****************************************************************
  Background:
  All JAX-WS handlers have a handleMessage method which you
  may use to query and change the XML message.
  If a JAX-WS handleMessage method returns false, the handler
  chain is reversed.
  
  For example if a JAX-WS client outbound handler returns false
  the following occurs:
     A) The handler chain is reversed.
     B) The outbound message becomes the inbound message.
     C) The handlers that were previously called for outbound
  processing are called for inbound processing.
     D) Flow of control returns to the customer's JAX-WS
  BindingProvider (Dispatch or Proxy)
  
  
  Problem:
  In some cases, the (B) processing fails.  The outbound message
  is lost and a different message is used for the inbound
  processing.   The result is unexpected behavior when the flow
  of control returns to the customer's JAX-WS BindingProvider (D).
  
  Important Note:
  Most customer handlers will not return false.  This scenario
  is most common if you are writing a test application to
  simulate a web service invocation.
  

Problem conclusion

• When a JAX-WS handler edits the XML message, the JAX-WS
  runtime stores this message for subsequent handler calls.
  However the handler chain reversal algorithm did not use this
  edit XML message for the inbound message.   Instead it used a
  stale (pre-edited) copy of the outbound message.
  
  The JAX-WS runtime is changed to correctly use the edited XML
  message when the handler chain is reversed
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 7.0.0.15.  Please refer to the Recommended Updates
  page for delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

Temporary fix

• Fix Error, see PM39817
  

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

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R700 PSY

     UP