PI80477: JAXB FAILS TO UNMARSHAL ARRAYS WITH CUSTOM TYPE INSIDE @XMLELEMENT ANNOTATION

Fixes are available

APAR status

Closed as program error.

Error description

Test showing the problem:

The Input XML is:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<BSSampleEvent><intArray>42</intArray><intArra y>13</intArray>
</BS SamplEvent>

Unmarshal snippet:

public static void main(String[] args) throws
UnsupportedEncodingException {
      BSSampleEvent result = JAXB.unmarshal(new
ByteArrayInputStream
("...".getBytes("UTF8")), BSSampleEvent.class);
      System.out.println("intArray out: " +
Arrays.toString(result.
getIntArray()));
      if (!Arrays.equals(new int[] {42, 13},
result.getIntArray())) {
         throw new AssertionError("Arrray not correct");
      }
   }

The expected result after unmarshalling is that the field
intArray is set to {43,13} but the actual result is null.

Local fix

Disable JAXB unmarshalling optimization by setting
com.ibm.xml.xlxp.jaxb.opti.level to 2 or 0.

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server                                      *
****************************************************************
* PROBLEM DESCRIPTION: JAXB produces null value when           *
*                      unmarshalling primitive type arrays     *
*                      annotated with @XMLElement annotation   *
*                      containing custom type.                 *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Problem is resolved and the to enable the fix requires a JVM
this system property to be set. Default value is false.
-Djaxb.fp.fallback.for.typed.arrays=true

Problem conclusion

The fix for this APAR is currently targeted for inclusion in
fix pack 8.0.0.14, 8.5.5.13 and 9.0.0.5.
Please refer to the Recommended Updates page for delivery
information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

There are 2 possible fixes:
1. Remove type attribute from @XMLElement annotation on the
primitive array
2. Enable com.ibm.xml.xlxp.jaxb.opti.level=2 system property

Comments

APAR Information

APAR number
PI80477
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-04-24
Closed date
2017-05-25
Last modified date
2017-05-25

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

R800 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
04 May 2022

Tips

PI80477: JAXB FAILS TO UNMARSHAL ARRAYS WITH CUSTOM TYPE INSIDE @XMLELEMENT ANNOTATION

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R800 PSY

Document Information

Share your feedback

Need support?