IZ95390: JAXELEMENT PRODUCING WRONG VALUE WITH XSI:NIL CHECK AFTER APPLYING APAR IV12669

APAR status

• Closed as program error.

Error description

• Error Message: When using nil values in XML messages (WAS Web
  Services) these are not correctly unmarshalled by the JAXB
  runtime. Also, JAXBElement xsi:nil check for the second
  invocation shows a different result than the first invocation
  (after application restart).
  .
  Stack Trace: N/A
  .
  N/A
  

Local fix

• N/A
  

Problem summary

• WAS WebService uses JDK inbuild JAXB with first invocation and
  for subsequent invocation it uses the IBM fastpath JAXB runtime.
  With first invocation JAXB runtime is seemed to returing wrong
  result while with second invocation the result seems to correct
  as per specification and API documentation.
  

Problem conclusion

• This defect will be fixed in:
  6.0.0 SR10
  .
  IBM JDK JAXB upgraded to return correct result with JAXBElement
  isNil check method.
  .
  To obtain the fix:
  Install build 20110413 or later
  

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

  JAVA CLASS LIBS

• Fixed component ID

  620700130

Applicable component levels

• R600 PSN

     UP