PM34264: BOTH REQUIRED ELEMENTS OF A CHOICE GROUP ARE CREATED WHEN USING XSD:CHOICE

APAR status

• Closed as program error.

Error description

• Both required elements of a choice group are created when using
  XSD:Choice.
  
  Exmaple XML Schema using choice group:
  
  <xsd:complexType name="ComplexElementsType">
    <xsd:choice>
     <xsd:element name="unorderedElements1"
  type="UnorderedElements" />
     <xsd:element name="unorderedElements2"
  type="UnorderedElements" />
    </xsd:choice>
   </xsd:complexType>
  
  Example XML output created when using choice group:
  
  <complexElements>
  <unorderedElements1></:unorderedElements1>
  <unorderedElements2>
  <unorderedElement1>111:</unorderedElement1>
  <unorderedElement2>222:</unorderedElement2>
  <unorderedElement3>333:</unorderedElement3>
  <unorderedElement4>444:</unorderedElement4>
  </unorderedElements2>
  </complexElements>
  
  Both the unorderedElements1 and unorderedElements2 elements are
  created ignoring that they are part of a choice group
  (xsd:choice).
  

Local fix

• WTXCQ - WTX00036973
  GK / GK
  Circumvention: None
  

Problem summary

• Users Affected:
  WebSphere Transformation Extender xerces parser customer using
  XML complex type choice group with required elements
  
  Problem Description:
  Prevent type tree mismatch error when using a complex type than
  contains a choice group that has 2 required elements.
  
  Platforms Affected:
  ALL
  

Problem conclusion

• For a complex type need to test if we are in a choice group
  before checking for required fields. If you have 2 required
  elements in a choice group only 1 is really required.
  
  Delivered in:
  8.2.0.6, 8.3.0.4
  

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

  WEBSPHERE DESIG

• Fixed component ID

  5724M4008

Applicable component levels

• R820 PSY

     UP

• R830 PSY

     UP