Abstract: Various methods, apparatuses/systems, and media for implementing an API design and development module are disclosed. A receiver receives inputs for designing a specification. Codes are generated from the API specification and necessary business logic is added. A processor pushes the specification along with the code to a source control which automatically triggers a continuous integration/continuous deployment (CI/CD) pipeline in response to pushing of the specification along with the code to the source control. The CI/CD pipeline automatically executes, through pre-defined configuration, each phase of an API development life cycle to develop the API based on the designed specification.

Abstract: Various methods, apparatuses/systems, and media for implementing an API design and development module are disclosed. A receiver receives inputs for designing a specification. Codes are generated from the API specification and necessary business logic is added. A processor pushes the specification along with the code to a source control which automatically triggers a continuous integration/continuous deployment (CI/CD) pipeline in response to pushing of the specification along with the code to the source control. The CI/CD pipeline automatically executes, through pre-defined configuration, each phase of an API development life cycle to develop the API based on the designed specification.

Abstract: A system for automatically generating request-specific backup contact information in an out of office message that automatically generates an out of office message with specific backup contact information based on an automatically determined correspondence between the contents of a received e-mail message and one or more responsibilities of the user an e-mail message is addressed to. A user interface object allows a user to specify one or more keywords for each different one of their roles/responsibilities, and to also specify corresponding backup contact information for each role/responsibility. Incoming e-mail messages are analyzed to detect the user's keywords used to identify one or more corresponding roles/responsibilities. Based on this detection of keywords in the received message and the correspondence of the detected keywords with role/responsibility back up contact information in the persistent storage, only relevant backup contact information is retrieved and included in the out of office reply.

Abstract: Class loader changes from at least one user-defined class loader to a bootstrap class loader are determined by a stack processing module during de-serialization of a serialized data object. A reference to each user-defined class loader is stored separately from a thread method frame stack in response to each determined change from the at least one user-defined class loader to the bootstrap class loader. For each user-defined class load operation of a user-defined class associated with the de-serialization of the serialized data object, a latest user-defined class loader (LUDCL) is identified using the stored reference and the user-defined class is loaded using the identified LUDCL.

Abstract: A system for fast rendering of an applet in a Web browser environment. A server process pre-determines the order in which the applet classes are loaded by the applet. The server process determines the classes of the applet that are required for applet start-up, and these startup classes are bundled into an initial JAR file on the server for the applet, along with a list of other class files belonging to the original JAR files. After the initial JAR file is downloaded, and while the JVM on the client system is loading the applet classes from the initial JAR file to bring up the applet, the rest of the applet classes (i.e. non-startup classes) are downloaded from the server to the client in the background. As each such non-startup class is received by the client system, it is loaded into the correct JAR file based on the class list.

Abstract: Class loader changes from at least one user-defined class loader to a bootstrap class loader are determined by a stack processing module during de-serialization of a serialized data object. A reference to each user-defined class loader is stored separately from a thread method frame stack in response to each determined change from the at least one user-defined class loader to the bootstrap class loader. For each user-defined class load operation of a user-defined class associated with the de-serialization of the serialized data object, a latest user-defined class loader (LUDCL) is identified using the stored reference and the user-defined class is loaded using the identified LUDCL.

Abstract: A system for automatically generating request-specific backup contact information in an out of office message that automatically generates an out of office message with specific backup contact information based on an automatically determined correspondence between the contents of a received e-mail message and one or more responsibilities of the user an e-mail message is addressed to. A user interface object allows a user to specify one or more keywords for each different one of their roles/responsibilities, and to also specify corresponding backup contact information for each role/responsibility. Incoming e-mail messages are analyzed to detect the user's keywords used to identify one or more corresponding roles/responsibilities. Based on this detection of keywords in the received message and the correspondence of the detected keywords with role/responsibility back up contact information in the persistent storage, only relevant backup contact information is retrieved and included in the out of office reply.

Abstract: A system for fast rendering of an applet in a Web browser environment. A server process pre-determines the order in which the applet classes are loaded by the applet. The server process determines the classes of the applet that are required for applet start-up, and these startup classes are bundled into an initial JAR file on the server for the applet, along with a list of other class files belonging to the original JAR files. After the initial JAR file is downloaded, and while the JVM on the client system is loading the applet classes from the initial JAR file to bring up the applet, the rest of the applet classes (i.e. non-startup classes) are downloaded from the server to the client in the background. As each such non-startup class is received by the client system, it is loaded into the correct JAR file based on the class list.