Software mechanism for efficient compiling and loading of java server pages (JSPs)

• US 20040073552A1
• Filed: 10/09/2002
• Published: 04/15/2004
• Est. Priority Date: 10/09/2002
• Status: Active Grant

• Current Assignee: LinkedIn Corporation (Microsoft Corporation)
• Original Assignee: International Business Machines Corporation
• Inventors: Smet, Arthur Douglas, Bailey, Byron Lewis
• Granted Patent: US 7,093,243 B2
• Time in Patent Office: Days
• US Class Current: 707/100
• CPC Class Codes: G06F 9/445 Program loading or initiating bootstrapping G06F9/4401; security arrangements for program loading or initiating G06F21/57
• CPC Class Codes: G06F 9/45516 Runtime code conversion or optimisation

Abstract

Method and apparatus for processing java server pages (JSPs) which reduces the delays resulting from a first time invocation of a JSP. One embodiment provides a method for processing JSPs for a java virtual machine (JVM), comprising: selecting one or more JSP files to be processed for the JVM; translating the JSP files to java source code files; inserting quick exit codes to java source code files; compiling java source code files to servlet class files; and loading servlet class files into the JVM.

Claims

1. A method for processing java server pages (JSPs) for a java virtual machine (JVM), comprising:

selecting at least one JSP files to be processed for the JVM;

translating the at least one JSP files to java source code files;

inserting quick exit codes to java source code files;

compiling java source code files to servlet class files; and

loading servlet class files into the JVM.

2. The method of claim 1, wherein the JSPs are processed during an initialization of a Web application.

3. The method of claim 1, further comprising invoking servlet class files which exceed a size threshold value.

4. The method of claim 1, further comprising generating a direct executable via just in time optimization.

5. The method of claim 1, further comprising spawning a plurality of threads to process the selected JSP files.

6. The method of claim 5, wherein a thread count initialization parameter specifies a number of threads to be spawned.

7. The method of claim 1, wherein the quick exit code checks for an initialization attribute which indicates whether to exit when a JSP is executed for a first time.

8. A computer readable medium containing a program which, when executed, performs an operation, comprising:

selecting one or more JSP files to be processed for a JVM;

translating the JSP files to java source code files;

inserting quick exit codes to java source code files;

compiling java source code files to servlet class files; and

loading servlet class files into the JVM.

9. The computer readable medium of claim 8, wherein the operation further comprises invoking servlet class files which exceed a size threshold value.

10. The computer readable medium of claim 8, wherein the operation further comprises generating a direct executable via just in time optimization.

11. The computer readable medium of claim 8, wherein the operation further comprises spawning a plurality of threads to process the selected JSP files.

12. The computer readable medium of claim 8, wherein the quick exit code checks for an initialization attribute which indicates whether to exit when a JSP is executed for a first time.

13. A computer for processing JavaServer pages (JSPs), comprising:

an application server computer comprising one or more processors and a memory, the memory containing a JSP processor and a Java Virtual Machine (JVM), wherein the JSP processor is configured to selectively load one or more JSP class files into the JVM prior to user requests for JSP files.

14. The computer of claim 13, wherein the memory further comprises a servlet engine for initializing a web application which utilizes the JSPs.

15. The computersystem of claim 14, wherein the servlet engine is configured to spawn a plurality of threads to process the JSP files

16. The computer of claim 13, wherein the JSP processor is configured to:

select one or more JSP files to be processed for a JVM;

translate the JSP files to java source code files;

insert quick exit codes to java source code files;

compile java source code files to servlet class files; and

load servlet class files into the JVM.

17. The computer of claim 13, wherein the JSP processor is further configured to invoke servlet class files which exceed a size threshold value.

18. The computer of claim 13, wherein the JSP processor is further configured to generate a direct executable via just in time optimization.

19. A method for processing JSPs for a JVM, comprising:

initializing a web application containing the JVM;

selecting one or more JSP files to be processed for the JVM;

translating the JSP files to java source code files;

inserting quick exit codes to java source code files;

compiling java source code files to servlet class files;

loading servlet class files into the JVM; and

invoking servlet class files which exceed a size threshold value.

20. The method of claim 19, further comprising generating a direct executable via just in time optimization.

21. The method of claim 19, further comprising spawning a plurality of threads to process the selected JSP files.

22. The method of claim 19, wherein the quick exit code checks for an initialization attribute which indicates whether to exit when a JSP is executed for a first time.

23. A method for processing a JSP for a JVM prior to a user request for the JSP, comprising:

loading the JSP into the JVM;

invoking the JSP; and

terminating execution of the JSP prior to execution of user codes in the JSP.

24. The method of claim 23, further comprising:

initializing a web application containing the JVM; and

selecting JSP to be processed for the JVM based on a size threshold parameter.

25. The method of claim 23, wherein the JSP is translated to a java source code file and compiled to a servlet class file, prior to loading into the JVM.

26. The method of claim 25, further comprising:

inserting quick exit codes to the java source code file, wherein the quick exit code checks for an initialization attribute which indicates whether to exit when a JSP is executed for a first time.