Java version incompatibility causes "Class not Found" Error in LANSA Composer

Date:21 April 2009
Product/Release:LANSA Composer V2.0
Abstract:Java version incompatibility causes "Class not Found" error
Submitted By:LANSA Technical Support

Description:

Previous versions of LANSA Composer compiled the generated Java code for Transformation Maps for target Java version 1.4.

To accommodate recent and future versions of Altova MapForce, this version has been changed such that: 

  • You can specify (in System Settings) the Java version to target
  • The default value (including for an upgraded installation) is now 1.5
  • If the JVM on your System i or Windows server is running at version 1.4, the compiled code that results when you prepare Transformation Maps with the default setting in this version of LANSA Composer will not be compatible with your JVM.

To address this, you should do one of the following:

  1. Change the "Java version for Transformation Maps" value in System Settings to be compatible with the JVM version you are using.

  2. Change the LANSA Integrator configuration on your System i or Windows server to use a JVM version 1.5 (or later). Refer to How to Confirm JAVA Version on System i for guidance in connection with your System i server.

Note: The Java code generated for maps created with MapForce 2009 or later will require at least Java version 1.5. Therefore the second option is recommended. If you do not choose this option now, it will become necessary at a later time. 

If the "Java version for Transformation Maps" value in System Settings is NOT compatible with the JVM version used by the LANSA Integrator instance, then you will receive errors when you run affected Transformation Maps. One such symptom is a "class not found" error in the JSM trace that refers to Java classes implemented in the transformation map.

Existing installations are quite likely to encounter this issue when running new or re-prepared Transformation Maps after upgrading to version 2.0 if:

  • LANSA Integrator is using JVM 1.4 on System i
  • The advice (as above) in the readme has not been followed