The GenRocket Runtime consists of a set of Jars that can be loaded and executed by a Java Virtual Machine (JVM) to load and run GenRocket Scenarios.
The GenRocket Runtime consists of the following set of Jars:
- GenRocket Runtime - Contains all the dependency Jars that are required by our core GenRocket Jars in a zip file.
- GenRocket Jar - Contains classes that interprets user command line input, performs license checking, packages requests and launches the GenRocket engine.
- GenRocket Engine Jar - Contains the core engine classes that runs GenRocket Scenarios
- GenRocket Generator Jar - Contains all GenRocket Generator classes
- GenRocket Receiver Jar - Contains all GenRocket Receiver classes
We also perform a checksum on our GenRocket Jar, GenRocket Engine Jar, GenRocket Generator Jar and GenRocket Receiver Jar.
Please see the sections below to learn more about Java byte code, Jars and the Java Runtime.
Java source files (.java) are read by the Java compiler, converted into byte code and stored to a binary (.class) file. These .class files are meant to be interpreted and executed by a Java virtual machine (JVM).
A JAR (Java ARchive) is a package file format typically used to aggregate many Java class files and associated metadata and resources (text, images, etc.) into one file for distribution. Jars are built on the ZIP format and typically have a .jar file extension.
The Java runtime environment is a piece of software that is designed to run other software. As the runtime environment for Java, the JRE contains the Java class libraries, the Java class loader, and the Java Virtual Machine. In this system:
- The class loader is responsible for correctly loading classes and connecting them with the core Java class libraries.
- The JVM is a virtual machine that enables a computer to run Java programs as well as programs written in other languages that are also compiled to Java byte code.
- The JRE is mainly a container for those other components and is responsible for orchestrating their activities.