PH52823: JAVA TRANSFORMATIONS INTRODUCING COMPILER ERRORS THAT DID NOT EXIST BEFORE

APAR status

• Closed as program error.

Error description

• When you import the code baseline to a Java project and resolve
  dependencies using a JAR file, there are no compiler errors but
  when you transform and run an immediate reverse transformation
  from UML to java, it introduces hundreds of compiler errors of
  'type mismatches' and/or unable to recognize operations or
  parameters with no code changes occurred.
  

Local fix

• There is no workaround
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * -                                                            *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * Integer default value gets converted to Integer Class object *
  * during Java to UML transformation.                           *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• Integer default value is not converted to Integer Class object
  and maintained as an Integer literal during Java to UML
  transformation.
  

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

  SW ARCHITECT WI

• Fixed component ID

  5724I7001

Applicable component levels