Method and device for loading classes and creating and accessing class objects

Abstract

The invention relates to a method and a device for loading classes and creating and accessing class objects, wherein the method used for loading the classes of network applications on a Java platform comprises the following steps: loading all the classes of the network applications into a Java virtual machine of the Java platform when deploying the network applications on the Java platform; and changing names of the classes which are loaded into the Java virtual machine and only used by the network applications. The utilization of the method and the device can load all the classes of the network applications with high performance and control the safe use of the classes and the safety access of the class objects.

Description

technical field [0001] The invention relates to a method and a device for loading classes and creating and accessing objects of the classes. Background technique [0002] With the continuous development of microelectronics technology, the integration of integrated circuits is increasing rapidly, and smart card technology is also developing faster and with greater capacity. NGMS (Next Generation Mega SIM: Next Generation Large-Capacity Subscriber Identity Module) card already has 1-2G flash memory, 64-128M RAM and 200MHz CPU, and corresponding high-speed communication mechanism, and the corresponding software system is also changing with each passing day. improvement. [0003] The biggest problem currently facing is that NGMS cards do not have user interface (UI) devices such as display screens, keyboards, speakers, etc. that are inherent in mobile terminals, which makes it very complicated for applications on NGMS cards to interact with users. , that is, the NGMS card need...

AI Technical Summary

Problems solved by technology

But this is not worth the candle for NGMS cards with limited resources. In other words, it is very likely that the resources occupied by a network application are not as much as the resources consumed by the security manager and user-defined class loader implemented by the network application. it's not worth the candle

[0012] The second problem is a performance problem

Each user-defined class loader will entrust its own parent class before searching for the class to be loaded according to the user-defined class loading directory, and will eventually trace back to the system class loader for processing, and then delegate down layer by layer To the user-defined class loader, this process is cumbersome and affects performance

In addition, the user-defined class loading directory may be a remote server or database, so when loading the class that needs to be loaded, it will go through a traversal search and remote loading process, which will also seriously consume resources

[0013] The third problem is security

The user-defined class loader mechanism allows different class loaders to load classes with the same name but different contents. However, the user-defined class loading directory is beyond the control of the system, so the class may come from an untrusted place

Therefore, when the user-defined class loader mechanism of the JavaSE platform is implemented on the JavaME platform, it may happen that the user-defined class maliciously overwrites the original system class of the JavaME platform, thus causing the system code in the JavaME platform to be executed. Violation of original class behavior

Images