Bug 21627 - Compiled class error on iSeries
Summary: Compiled class error on iSeries
Status: RESOLVED WORKSFORME
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows 2000
: P3 major (vote)
Target Milestone: 2.1 M1   Edit
Assignee: Philipe Mulet CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-07-16 12:26 EDT by Kevin CLA
Modified: 2002-09-10 08:51 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kevin CLA 2002-07-16 12:26:04 EDT
Compiled classes using V2.0 and deployed to iSeries IFS running V4.R5.M0 and 
get UnSupportedClass error even for simple helloworld app. Also run WSAD 4.0 
imported project into there, compiled and deployed with exactly same IDE setup 
(JDK etc...) and it works fine. I assume that the compiler in Eclipse is not 
creating the same class object way as WSAD's compiler does. Both IDE compiled 
objects run fine on iSeries V5.R1.M0 though, unfortunately my platform is not 
to be upgraded yet and WSAD is trial copy.
Comment 1 Philipe Mulet CLA 2002-07-16 16:26:59 EDT
WSAD is built on top of Eclipse, so you are likely using the same compiler, 
simply a different version of it.

The Eclipse R2.0 compiler can be toggled for 1.3 or 1.4 compliance (1.3 is the 
default). When compiling in 1.4 mode, the classfile are targeted for a 1.4 VM 
or better, and if attempting to run the classfile on a 1.3 target, then the VM 
will refuse to load them, arguing a format error (when actually only the 
classfile tag is the issue).

This is a VM restriction which we have to be compliant with. For instance, it 
enforces the 1.4 support for assertions is around at runtime (need extra 
classes in system libraries).

Under the compiler compliance setting, you can tell it to use 1.4 compliance 
mode, but 1.3 source mode and 1.1 target mode (in the same way as you can use a 
jdk1.4 javac in "-source 1.3" mode). Assertions are no longer supported, but 
the classfile can then run on a older target.

If you are seeing a different problem, please elaborate on your symptoms, you 
could have found a bug. But having even 'hello world' fail likely indicate a 
major issue as the one I described above.
Comment 2 Philipe Mulet CLA 2002-07-18 06:02:02 EDT
Is it ok to close, or could you provide more information ?
Comment 3 Philipe Mulet CLA 2002-07-25 08:20:59 EDT
Closing, please reopen if you have more information to provide.