PH03014: A PROPERTY IS SET IN THE REQUESTCONTEXT, BUT THE INTERCEPTOR DOES NOT READ THIS PROPERTY RESULTING IN A NULLPOINTEREXCEPTI

18.0.0.4: WebSphere Application Server Liberty 18.0.0.4
19.0.0.1: WebSphere Application Server Liberty 19.0.0.1
19.0.0.2: WebSphere Application Server Liberty 19.0.0.2
19.0.0.3: WebSphere Application Server Liberty 19.0.0.3
19.0.0.4: WebSphere Application Server Liberty 19.0.0.4
19.0.0.5: WebSphere Application Server Liberty 19.0.0.5
19.0.0.6: WebSphere Application Server Liberty 19.0.0.6
19.0.0.7: WebSphere Application Server Liberty 19.0.0.7
19.0.0.8: WebSphere Application Server Liberty 19.0.0.8
19.0.0.9: WebSphere Application Server Liberty 19.0.0.9
19.0.0.10: WebSphere Application Server Liberty 19.0.0.10
19.0.0.11: WebSphere Application Server Liberty 19.0.0.11
19.0.0.12: WebSphere Application Server Liberty 19.0.0.12
20.0.0.1: WebSphere Application Server Liberty 20.0.0.1
20.0.0.2: WebSphere Application Server Liberty 20.0.0.2
20.0.0.3: WebSphere Application Server Liberty 20.0.0.3
20.0.0.4: WebSphere Application Server Liberty 20.0.0.4
20.0.0.5: WebSphere Application Server Liberty 20.0.0.5

APAR status

• Closed as program error.

Error description

• Using "cxf.add.attachments = true" in the MessageContext
  works
  fine but for one specific usecase where it does not work:
  When using Dispatch-API, you can only access the
  RequestContext. So they tried to define the property this
  way:
  
  BindingProvider bp = (BindingProvider) _proxy;
  bp.getRequestContext().put("cxf.add.attachments",
  Boolean.TRUE);
  
  The property is set in the RequestContext, but the
  interceptor
  does not read this property and results in a
  NullPointerException
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  IBM WebSphere Application Server Liberty    *
  *                  users of JAX-WS Web Services                *
  ****************************************************************
  * PROBLEM DESCRIPTION: SOAP attachments in a Web service       *
  *                      request were not processed by Web       *
  *                      services CXF code                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Some types of binary attachments sent in a Web Services SOAP
  request were not processed by the Web services CXF code in
  Liberty.  The CXF code only processed MTOM attachments in the
  SOAP request.
  

Problem conclusion

• The CXF attachment interceptors did not recognize attachments
  sent in a SOAP request that were not MTOM attachments. This
  problem was resolved by adding a custom property
  "cxf.add.attachments" that needs to be set in the request
  context of the SOAP message.
  
  The fix for this APAR is currently targeted for inclusion in fix
  pack 18.0.0.4.  Please refer to the Recommended Updates page for
  delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

Temporary fix

• There is no work around available for this problem.
  

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

  LIBERTY PROFILE

• Fixed component ID

  5724J0814

Applicable component levels

• RCD0 PSY

     UP