PM54684: EST Mapping Editor validation and/or Generate Conversion Code action may fail if mapping members of derived XSD complex type

Rational Developer for System z 8.5

APAR status

• Closed as program error.

Error description

• EST Mapping Editor validation and/or Generate Conversion Code
  action may fail when mapping members of derived XSD complex
  types.
  
  
  The User Interface cannot map certain elements from a COBOL
  copybook to a XML schema when the same XML element names are
  present in different levels of the schema.
  Also, the UI does not generate the XML converter code and fails
  with message:
  'CRRZX0073E The import of language types failed
                       because of an internal error.  See
                       the log file in the current workspace.'
  

Local fix

• Until this is addressed:
  Do not use complex types that are derived from other complex
  types.
  Or - Edit the mapping file manually using the XML editor and
  add the mappings.
  

Problem summary

• There are two related problems that are covered by this APAR:1.
  The Mapping Editor Validation logic will mistake an element as
  being "already mapped" when the element is a child of multiple
  elements by means of complex type derivation.  For
  example,Assume:  a.) There exists a complex type T1 that
  contains an element E1.  b.) There exist two complex types T2
  and T3 that both extend (derive from) T1.  c.) There exist two
  elements P1 and P2 where P1 is of type of T2 and P2 is of type
  T3. (Therefore, P1 and P2 contain an element E1). Given the
  above assumptions, the Mapping Editor Validation logic will
  incorrectly consider P2/E1 already mapped if P1/E1 is currently
  mapped.2. The meet-in-middle "Generate Conversion Code" action
  fails with a ModelRebuilderException when mapping a member of a
  derived complex type.For example,Assume:  a.) There exists a
  complex type T1 that contains elements E1, E2, E3.  b.) There
  exist two complex types T2 and T3 that both extend (derive from)
  T1.  c.) There exist two elements P1 and P2 where P1 is of type
  of T2 and P2 is of type T3.  (Therefore, P1 and P2 contain
  elements E1, E2, and E3).  d.) P1/E1 is mapped using the Mapping
  Editor.  e.) P2/E1 is mapped by manually editing the Mapping
  Session file (normally disallowed by problem #1).  f.) P1/E2 is
  mapped using the Mapping Editor. Given the above assumptions,
  the "Generation Conversion Code" logic will produce an internal
  set of mappings that is correct except for one or more NULL
  mappings. These NULL mappings are an artifact of lack of support
  for derived complex types in the Mapping Editor interface to the
  code generator, and ultimately cause the code generator to fail
  when building an internal model.
  

Problem conclusion

• The mapping editor problem and the code generation problem are
  fixed (see problem summary for more information).
  
  The problem listed in this APAR has been resolved with
  IBM Rational Developer for System z V8.0.3.2 Fix Pack which
  is available from the Recommended Fixes support download page:
  http://www-1.ibm.com/support/docview.wss?rs=2294&uid=swg27006335
  

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

  RATL DEV FOR SY

• Fixed component ID

  5724T0700

Applicable component levels

• R803 PSY

     UP