PI11949: WS-ADRESSING FEATURE DID NOT WORK CORRECTLY WITH JDK7

8.5.5.2: WebSphere Application Server V8.5.5 Fix Pack 2
8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
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.14: WebSphere Application Server V8.5.5 Fix Pack 14
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 program error.

Error description

• When running Liberty profile with JDK7, JAX-WS applications
  using WS-Adressing don't work correctly.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  IBM WebSphere Application Server Liberty    *
  *                  Profile users of JAX-WS web services        *
  *                  applications                                *
  ****************************************************************
  * PROBLEM DESCRIPTION: When running Liberty profile with       *
  *                      JDK7, JAX-WS applications using         *
  *                      WS-Adressing don't work as expected.    *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When running Liberty profile with JDK7, JAX-WS applications
  using the WS-Adressing feature provided by JAX-WS 2.2 don't
  work as expected.
  For example, a Web Service endpoint expects a non anonymous
  response through using @Addressing annotation or deployment
  descriptor configuration as following:
  @Addressing annotation:
  @Addressing(enabled=true, required=true,
  responses=AddressingFeature.Responses.NON_ANONYMOUS)
  "addressing" element in the deployment descriptor:
  <addressing>
  <enabled>true</enabled>
  <required>true</required>
  <responses>NON_ANONYMOUS</responses>
  </addressing>
  Then the SOAP header of the incoming SOAP request, with an
  annonymous response address specified should be regarded as an
  invalid SOAP header. But with Liberty profile using JDK7, this
  SOAP header was incorrectly regarded as valid.
  

Problem conclusion

• When using JDK7 and enabling the appSecurity feature, the
  JAX-WS engine failed to detect the runtime as JAX-WS 2.2
  compliant due to a classload problem. This then caused the
  WS-Addressing feature to function incorrectly.
  
  The IBM JAX-WS engine for Liberty profile has been changed to
  correct the classload problem and correctly enable the
  WS-Adressing feature provided by JAX-WS 2.2.
  
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.5.5.2. 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

  LIBERTY PROFILE

• Fixed component ID

  5724J0814

Applicable component levels

• R850 PSY

     UP