Running a constant pool is part of the method area. In addition to the class version, fields, methods, interfaces, and other descriptive information, there is also a constant pool, which holds the various literal and symbolic references generated during the compilation period, which will be stored in the run-time pool of the method area after the class is loaded.
The Java Virtual machine's format for each part of the class file (which naturally also includes the Chang) is severely defined, and each byte used to store which data must conform to the requirements of the specification so that it is recognized, loaded, and executed by the virtual machine. But for running a constant pool, the Java Virtual Machine specification does not require any detail. In general, in addition to saving the symbolic references described in the class file, the translated direct references are also stored in the run-time-constant pool.
Another important feature of running a constant pool relative to a class file's const pool is dynamic, and the Java language must require constants to be generated only by the compiler, which means that the content of the constant pool in the class file is not pre-placed to run the const pool in the method area. It is also possible to put a new constant pool in the pool during the run, which is more than the Intern () method of the string class used by open people.
Java run-time-constant pool