Preverifying

[komomo]

In Preverifying Class Files,
Because the memory on small devices is so scarce, MIDP (actually, CLDC) specifies that bytecode verification be split into two pieces. Somewhere off the device, a preverify step is performed. The device itself is only required to do a lightweight second verification step before loading classes.
That is what I read from a book.
According to that, although we are running a program successfully in an emulator, it may not work in a real device? Because we do only a preverify step before we test in an emulator?

[raj_J2ME]

In Preverifying Class Files,
Because the memory on small devices is so scarce, MIDP (actually, CLDC) specifies that bytecode verification be split into two pieces. Somewhere off the device, a preverify step is performed. The device itself is only required to do a lightweight second verification step before loading classes.
That is what I read from a book.
According to that, although we are running a program successfully in an emulator, it may not work in a real device? Because we do only a preverify step before we test in an emulator?

Correct indeed, when you will develop the apps and will be a experienced developer then you will face many situation like this and probably you will start a thread for the workaround purposals...

[ektasrv]

Refer to http://en.wikibooks.org/wiki/J2ME_Pr...Dlet_Preverify
for more info on prefification.
We need to do this preferfication step as a part of the build process to prepare the final JAR which we deploy on the real device also, just like you do on emulator. Its not that we skip this step when we test on real device.

[grahamhughes]

Bytecode verification occurs in two stages:

1. Preverification: this is done at build time, by running the preverifier tool.

2. Verification: this is done by the Java Virtual Machine, either in the emulator or on the device (there is no difference here).

Graham.