Preverification

Preverification is the step to generate the stackmap information in the classfile. The stackmap information is necessary for J2ME CLDC devices to verify that the midlets are free from corruption, and therefore pose no security risks. In a typical mobile application and game development environment without mBooster, the preverification is performed by Sun's preverifier in the Wirless Toolkit, or a preverfier bundled with the handset SDK.

By default mBooster will automatically generate the stackmap information after optimizing classfiles through one of two methods described below. However it is possible for the user to disable automatic stackmap generation through setting the PREVERIFIER.ENABLED property.

mBooster offers two choices in the method to generate stackmaps as configured by the PREVERIFIER.METHOD property:

Preverifier	Comments
INTERNAL	(Recommended)  The internal preverifier is designed for minimizing the generated stackmap and will typically generate more compact stackmaps than those generated by Sun's preverifier.
EXTERNAL	mBoooster can call an external preverifier (such as the preverifier in Sun's Wireless Toolkit) Note: Disabled in the Evaluation Version

The preverification step can be configured through this set of properties.

— Previous page – Contents – Next page —